Repository intelligence
Reading a codebase well enough to work inside it: structure, conventions, dependencies and the parts that matter to the change being made.
Software engineering capability
ZylCode
Repository intelligence, mission planning, bounded agents, artifacts, tests, evidence and delivery — a software engineering capability whose output is meant to be reviewed, not trusted on sight.
DevelopingPlacement under reviewDeveloper Preview waitlist
What this is
Engineering work with the receipts attached
ZylCode is the Zylvex software engineering capability: it understands a repository, plans the work, runs bounded agents against a defined task, and produces artifacts, tests and evidence that a person can review. The point is not speed for its own sake — it is a change you can justify. Its portfolio placement is under review (ADR-013), and this page says so rather than pretending the question has been settled.
Mission planning
Turning an objective into a plan with explicit scope, before any agent is let loose on the repository.
Bounded agents
Agents that operate inside declared limits — a defined task, a defined surface, a defined stopping point.
Artifacts
The output of a run: diffs, files and explanations produced as reviewable objects rather than as noise.
Tests and evidence
Tests run and results recorded, so a reviewer can see what was checked instead of taking a summary on faith.
Delivery
The last step — getting reviewed, tested work into the repository in a form another engineer can pick up.
The rule that governs it
Generated output is an offer, not a conclusion. Tests and evidence exist so a reviewer can reject the offer. A run that nobody checked has not delivered anything.
What this is not yet
The limits, stated plainly
ZylCode sits in an unusual position: in development, with its place in the portfolio still under review. These are the boundaries of what may be said about it.
Not released
There is no ZylCode download and no hosted service. What exists is a Developer Preview waitlist — a first-party Zylvex page, linked from here, where you leave an email address and hear back when invite-only seats open. Nothing beyond that is implied.
Portfolio placement is under review
Architecture decision record ADR-013 is still reviewing where ZylCode sits in the portfolio. This page states that openly rather than presenting a settled position.
No tool count is claimed
No tool-count figure appears anywhere in the company records, and none is made here. Capability is described by what it covers, not by a number.
Product page and development record
ZylCode now has a page under /products/zylcode/ covering what the product is, how it works, its current status and the Developer Preview link. This page stays the development record — dated milestones and status basis; that one is the product overview.
Output is meant to be reviewed
Nothing in ZylCode is presented as trusted on sight. Evidence and tests exist precisely so a human can decide whether a change is sound.
Not an initiative
ZylCode is treated as a product in the portfolio taxonomy. Programmes such as AERI are kept separate and are never counted as products.
Development record
What the repository shows, as at October 2026
These are dated engineering milestones from ZylCode's own record. They describe work that exists in the repository — not features anyone can reach. None of them is a release, and none is offered for download or use.
Software factory foundation
In developmentRecorded 6 October 2026
A dependency-aware task graph with durable job lifecycle and store, plus a runner that produces reviewable evidence and an end-to-end vertical slice exercising the whole path. A final owner gate report was written for this wave.
Repository intelligence
Re-opened on reviewRecorded 29 September 2026
Reading a repository well enough to work inside it, moved off prototype. Its acceptance milestone was deliberately reopened rather than closed, so this page reports it as under review instead of as finished.
Executable agent tools
In developmentRecorded 3 October 2026
Built-in agent tools made genuinely runnable, with their behaviour stated honestly rather than described optimistically.
Graded capability census
DocumentedRecorded 6 October 2026
An inventory in which every capability carries one explicit grade, so partial work can be reported as partial. It is the reason this page can state plainly what is not yet true.
How capability is graded
Every capability in the repository carries one grade drawn from a fixed vocabulary — runtime-verified, tested, wired, scaffolded, interface-only, not implemented and blocked. Nothing is recorded at a level its evidence does not support, and a blocked entry is never used as a synonym for finished. That discipline is what lets this page stay specific without overpromising.
Component workstream
Natlas — N-ATLAS integration
Natlas is the ZylCode workstream that connects ZylCode to N-ATLAS, a Nigerian multilingual language model, as a first-class provider behind its own dedicated transport seam. It sits inside ZylCode rather than beside it: it is component architecture, not a separate product in the portfolio.
What is built
A provider transport, configuration and authentication boundary, request and response handling, typed errors that are never coerced to success, intent interpretation into a validated task graph, and a factory handoff. A developer SDK and an interactive playground ship alongside it.
What is verified
The architecture is implemented and covered by committed tests. A genuine N-ATLAS round trip was captured on 7 October 2026, and a controlled bridge endpoint was verified healthy on 8 October 2026. Endpoint capacity is quota-limited, so sustained invocation is not assumed — a stated limit, not a claim that the integration is finished.
Why N-ATLAS specifically
Multilingual behaviour matters for Nigerian developer tooling, so the workstream includes a validation harness covering Yoruba and Nigerian Pidgin comprehension alongside English.
Status of this workstream
The workstream prepared an entry for the public N-ATLAS Challenge, problem statement PS1 (Developer Infrastructure), under the Innovation & Enterprise track; the submission window closed on 12 October 2026. On 8 October 2026 the workstream reached a release candidate: its competition test suite passed 61 of 61 without credentials, and a beta tester quickstart was written so an outsider can reproduce the run. As at 8 October 2026 no submission had been made and no external result existed. No award, selection, endorsement or outcome is claimed, and this workstream does not make ZylCode generally available — it is not in the product user interface and no ZylCode download exists.
Where this comes from
Status basis
The portfolio taxonomy in the site reorganisation baseline record
That record lists ZylCode as a product whose portfolio placement is under review under architecture decision record ADR-013 — implemented, with availability not verified — and requires this page to carry honest status labels. That record also noted the product index then contained no ZylCode entry — the index gained one when ZylCode's product page opened in October 2026.
Why the wording is cautious
When a record says placement is under review, the public page has to say placement is under review. Records are held by Zylvex Technologies Limited; nothing here is promoted from a review into a claim.
Elsewhere in the ecosystem
Sibling entries
ZylForge
DevelopingEngineering and fabrication operating system
Read moreZylMind
PlannedPlanned reasoning and assistance layer
Read moreZylLearn
PlannedPlanned engineering education product family
Read moreZylPro
PlannedPlanned paid entitlement tier
Read moreZylPass
PlannedPlanned identity, access and credentials layer
Read more