The active research, product and delivery programmes I direct. Each moves through defined
technical, partner and operating gates; the record below makes clear which decisions have been
made and which still depend on evidence. Previous employment is listed separately below.
Updated: 14 October 2026.
Delivery and development
Work is organised by the next decision it must support, from validation to delivery.
September 2026 — present
Planning
Quantum-control certification under partial model information
Technical study complete; general verification method under development
Conceptual model-set study, not a physical experiment. The analytic result and its assumptions are documented in the linked research note.
I developed a research formulation for certifying task performance across all physical models compatible with restricted quantum measurements. A completed one-qubit study demonstrates a global Hamiltonian sign ambiguity, an exact task-specific 0.50 fidelity ceiling, and a synthetic equal-shot comparison in which a discriminating readout removes the relevant ambiguity.
Working sequence3 steps
01
Define the physical model, experiment library, control task and finite-data compatible set without dropping disconnected model branches.
02
Separate statistical model-set coverage from a deterministic worst-case performance bound; retain empty or inconsistent sets as explicit outcomes.
03
Build and independently check a low-dimensional verifier, then compare measurement designs by improvement in certified performance under matched shot, time and compute budgets.
The completed calculation is analytic and synthetic. It is not a quantum-hardware result, a general certification theorem, an adaptive-policy benchmark, a peer-reviewed paper or a funded collaboration. Wider control classes and open-system dynamics require separate analysis.
July 2026 — present
Planning
QFlow productisation and education pilot planning
Detailed pilot planning
Public product or programme visual; status and claim boundary are stated below.
A documented external product review moved QFlow into detailed planning for a potential education-focused pilot. A separate controlled education record covers a cohort of 30 people; that number is not presented as 30 active users.
Working sequence3 steps
01
Keep the brief, circuit, generated source, provider route, run context and evidence in one reviewable record.
02
Define the teaching scope, access controls, supervision model and acceptance criteria before any pilot starts.
03
Continue provider strategy and enablement work while keeping credentials and consequential execution user-controlled.
This is product review and pilot planning. It does not establish procurement, deployment, a completed pilot, paid adoption or a university partnership agreement.
2026 — present
Planning
NODERIQ consortium and research programme
Partner gates and proposal development
Public product or programme visual; status and claim boundary are stated below.
Neura Parse is coordinating a planned three-company international research structure around governed edge intelligence, resilient networks and a robotics pilot. The working baseline is 30 months, 240 person-months, €2.10 million in eligible cost and a TRL 4 to 6 path.
Working sequence3 steps
01
Select the third pilot partner through capability, funding, IP, safety and delivery gates.
02
Lock work packages, partner effort, national funding routes and co-finance evidence.
03
Run evaluator crosswalk, claim review and submission QA before any formal proposal is sent.
The duration, effort, budget and maturity figures are proposal baselines. No funding decision, executed consortium agreement, completed proof of concept or deployment is claimed.
August 2026 — present
Delivery
Governed enterprise AI delivery
Confidentiality gate complete; service scope gated
No public project image. The visual record is withheld because this work includes employer or counterparty-confidential material.
A private enterprise engagement is being run through a controlled sequence for operational data, deterministic analysis, AI-assisted explanation and accountable human decisions. The counterparty and private work package remain confidential.
Working sequence3 steps
01
Complete the mutual confidentiality gate before access, disclosure or technical work.
02
Lock the service framework, data responsibilities, security boundary and intellectual-property terms.
03
Authorize work through bounded work orders, then retain acceptance and decision evidence for each delivery.
The mutual confidentiality step is complete. This page does not identify the counterparty, publish contract terms or imply that later service and deployment gates are already complete.
2025 — present
Public release
TaskNebula public product maintenance
Open-source release line
Public product or programme visual; status and claim boundary are stated below.
TaskNebula is the most-used public repository in the portfolio. On 3 September 2026 the public records showed 8,919 Docker pull events, 77 Docker tags, 28 GitHub releases, 40 stars, 10 forks and 69 commits attributed to Bayram Eker.
Working sequence3 steps
01
Maintain the self-hosted coordination surface and Docker release path.
02
Keep agent ownership, approval gates and inspectable operations as defaults.
03
Publish release and repository records so activity can be checked independently.
Docker pulls are registry pull events. They are not unique users, installations, servers, customers or active deployments.
December 2025 — present
Market development
Singapore and APAC market development
Discovery and partner qualification
Public product or programme visual; status and claim boundary are stated below.
Short Singapore visits supported APAC market discovery for NowFlow and NeuraOS. A requested company overview was reviewed by a Singapore public-sector technology organisation, and the current work is to qualify independent business partners and real end-user problems.
Working sequence3 steps
01
Separate market discovery from customer, partner and deployment claims.
02
Qualify organisations for technical contribution, funding route and end-user access.
03
Turn only partner-approved problems into bounded work packages and measurable validation plans.
Prior travel, correspondence and overview review do not establish procurement, a commercial partner, a paid engagement or a deployment.
Previous professional work
Earlier employment and project responsibilities, with their end dates.
2025 — September 2026
Past experience
Agentic software testing and enterprise AI
Former Project Manager at NETAŞ · left September 2026
No public project image. The visual record is withheld because this work includes employer or counterparty-confidential material.
As Project Manager at NETAŞ, I managed requirements, development tasks, evaluation and release planning for enterprise AI and software-testing projects. I left the company in September 2026.
Working sequence3 steps
01
Turned product goals into requirements and development tasks.
02
Defined evaluation, human-oversight and reliability checks before release.
03
Coordinated team delivery, reviewed test results and resolved production constraints.
Employer-confidential product names, roadmaps, customer information and internal performance records are not published here.
R&D and funding routes
Open routes under evaluation. These are gates and options, not applications or outcomes.
Preferred preparation route
IUK
UK–Singapore CR&D 2026
NODERIQ · NowFlow · NeuraOS
Next gate
Secure an eligible Singapore business partner and a partner-approved industrial robotics problem before drafting a submission.
This is a route under evaluation, not an application, partnership or funding outcome.
Publication boundary
This page intentionally excludes counterparty and individual names, application identifiers,
correspondence metadata, private contract terms, customer data and employer-confidential
roadmaps. A recorded discussion is not described as a partnership; a planned pilot is not a
deployment; an open funding route is not a submitted or funded project.
