Exact project consent
Source tests cover explicit, project-scoped delegation grants, revocation before execution, and redacted audit records. A live installation remains to be verified.
Your tools. Your infrastructure.
Careful coordination.
Clear boundaries.
Evidence first.
Yonca is a local-first coordination product in active development. This page distinguishes source-tested behavior from work that still needs a live installation and acceptance check.
Source-tested capabilities · live deployment verification pending
Lead agentPlan · decide · coordinate
ImplementationReviewVerification
Proposed coordination across configured accounts and machines
Continuity recordDecisions, results and next steps — pending live verification
Yonca / Capability status
What the evidence supports today.
“Source-tested” means code and tests support the behavior. It does not mean that a production fleet, account, or host has been verified live.
Accounts, budgets & rerouting
Source tests cover account normalization, budget changes, selected-account rechecks, and consent for quota rerouting. Live account identities and authentication are not verified here.
Machine mapping
Source tests cover a configured local project mapping to its remote workspace and denial before remote execution for an unapproved sibling project. Each machine still needs live checks.
Managed message continuation
Source tests cover a managed continuation boundary and allowlist revocation before work begins. Live delivery and other connection modes remain to be verified separately.
Continuity & memory migration
State, cursor, continuity, and installation paths have partial source and test coverage. The intended data source, privacy boundary, import repeatability, and restore behavior are roadmap work.
Independent review chain
A complete independent review chain tied to each revision still needs acceptance evidence. It is a roadmap item, not a current operational claim.
Local runtime capacity
Hardware observation alone is not a working local runtime. Endpoint, runtime support, inventory, isolation, and bounded acceptance checks must come first.
Four-state operations
Clear installed, tested, deployed, and unknown states are planned for the product experience. The discipline is not yet a verified public control.
09 / Partially source-tested · roadmap
Backup & recovery
Backup and recovery behavior has partial source and test coverage. No fresh inventory, destination verification, retention check, or clean restore exercise is evidenced here.
A completed copy is not a tested restore. Backup claims stay on the roadmap until those checks are complete.
Build with
the evidence visible.
Yonca is being developed step by step. This page is a capability status, not proof that a private deployment is installed or operating.
to@ate.sh ↗