Home / Current work
What I am building, delivering and testing now. Each item separates completed work from the next gate, and a plan from an outcome. Snapshot: 3 September 2026.
Product work, professional delivery, public releases and market development.
July 2026 — present
Planning
Detailed pilot planning
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 sequence 3 steps
Keep the brief, circuit, generated source, provider route, run context and evidence in one reviewable record.
Define the teaching scope, access controls, supervision model and acceptance criteria before any pilot starts.
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
Partner gates and proposal development
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 sequence 3 steps
Select the third pilot partner through capability, funding, IP, safety and delivery gates.
Lock work packages, partner effort, national funding routes and co-finance evidence.
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
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 sequence 3 steps
Complete the mutual confidentiality gate before access, disclosure or technical work.
Lock the service framework, data responsibilities, security boundary and intellectual-property terms.
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
Delivery
Project leadership and architecture
No public project image. The visual record is withheld because this work includes employer or counterparty-confidential material.
Current professional work covers requirements, architecture, backlog decomposition, competitor analysis, evaluation and delivery controls for agentic software-testing and enterprise AI products.
Working sequence 3 steps
Turn product goals into bounded requirements and architecture decisions.
Define evaluation, human-oversight and reliability controls before release decisions.
Coordinate team delivery, review evidence and resolve production constraints.
Employer-confidential product names, roadmaps, customer information and internal performance records are not published here.
2025 — present
Public release
Open-source release line
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 sequence 3 steps
Maintain the self-hosted coordination surface and Docker release path.
Keep agent ownership, approval gates and inspectable operations as defaults.
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
Discovery and partner qualification
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 sequence 3 steps
Separate market discovery from customer, partner and deployment claims.
Qualify organisations for technical contribution, funding route and end-user access.
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.
Open routes under evaluation. These are gates and options, not applications or outcomes.
Preferred preparation route
NODERIQ · NowFlow · NeuraOS
Next gate
Secure an eligible Singapore business partner and a partner-approved industrial robotics problem before drafting a submission.
No application has been submitted and no partner has approved the concept.
Time-boxed go/no-go review
QFlow Studio
Next gate
Proceed only with a UK quantum collaborator, a real problem owner, one bounded use case and a fair classical-baseline plan.
QFlow is an assurance layer, not a substitute for the problem-specific quantum application required by the call.
Investor traction gate
NODERIQ
Next gate
Test fit with selected investor partners before preparing an application or treating aligned investment as available.
Current investor discussions are not an invitation, term sheet, committed investment or grant decision.
Conditional capacity route
Assured autonomous systems capability
Next gate
Progress only with an eligible UK knowledge-base lead, at least two business FTEs and a fundable capability-building plan.
This is a route under evaluation, not an application, partnership or funding outcome.
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.