01 /
Intent before action
The plan should be understandable and reviewable before any remote change happens.
ARCHITECTURE · HONEST STATUS
Designed for
deliberate delivery.
A governed workflow model lives behind the Lite preview experience. Here is what the architecture intends—and what has actually been verified.
01 THE SYSTEM
A human-in-the-loop
delivery model.
01 · VERIFIEDPlanStructure intent into a Sealed Preview.
→02 · SOURCE CAPABILITYAuditReview the exact Preview and its evidence.
→03 · SOURCE CAPABILITYHuman ApprovalExplicit approval of one Preview revision.
→04 · NOT INTEGRATION-ACCEPTEDApplyBounded writes, receipts, recovery.
The source implements more of the pipeline than the public Lite demonstration validates. A source-level capability does not equal an integration-accepted, released service.
02 EVIDENCE, NOT HYPE
Know what's
real today.
This is a snapshot of evidence from one specific local Host setup, not a compatibility promise for every environment.
CapabilityEvidence
Natural language → Sealed Preview✓ Verified · Codex CLI
Preview → copyable Issue Markdown✓ Verified locally · integration pending
Conceptual preview without GitHub writes✓ Verified · one workflow
Automatic multi-Issue planning UX◯ Further product test pending
Strict Preview-only Host tool isolation◯ Not established
Real GitHub Apply integration acceptance◯ Blocked / not completed
Formal public release◯ Not released
03 GUIDING PRINCIPLES
02 /
Explicit human decisions
Approval is not inferred from a model response or a successful preview.
03 /
Evidence over assertions
Preview, revision, audit evidence, and execution results are separate things.
04 /
Stop on ambiguity
Unknown write outcomes should not become blind automatic retries.
Prefer the full implementation-oriented documentation?
Read architecture & lifecycle