NEXT temporary contract 3.25 — Domain-by-domain IDE/ETO obligations and full-path gates
01Temporary normative staging unit. Its body is the accepted architecture from refined plan revision 4, section 3.25. Before production code cites this law, promote the relevant clauses into permanent specifications. This file is consumed only after semantic coverage, implemented behavior and retained evidence are accepted. The task/retirement checker cannot perform semantic acceptance.
02These rows revise the delivery contract of existing features; they are not a plugin feature list or an IDE MVP. Each domain retains its implementation milestone and gains a required external-access proof before its programme exit.
03Requirement: | Domain / owner | Externally inspectable models | Required external actions and closure proof | |---|---|---| | Sources/facts/requirements M-01/M-02/M-04 | Classified raw/projection resources, exact locations/proofs, relations/refinements/coverage/closure and diagnostics | Same-snapshot navigation/search/references and buffer-aware analysis; structured scaffold/answer/promote/close and exact stale/partial errors | | Selection/install M-05 | All root requests, candidates/rejections, options/effects, selected edges/lock, visible-world and freshness reasons | Discover/select/prepare/install/update/reinstall/remove, typed NeedsSelection, reverse-dependency effects, no hidden TTY/default | | Tree/boot M-06 | Complete package/occurrence graph, visibility provenance, stage carriers, source mapping, costs and preview scenarios | Tree/children/explain/compare/capture/export by snapshot; all text-only provenance becomes structured; no absent≡unreadable/unresolved≡unchecked | | Lifecycle/change M-03/M-04/M-11 | Request/run/input/output/pre/post transition, parked work, evidence/closure and failure journal | Prepare/run/adopt/observe/control/reconnect/recover under actual workspace limits; repeated request never duplicates production | | Adapters/extensions/derivatives M-08/M-09/M-10 | Schemas/capabilities/selection, grants, resource ownership, base/local/result and active content provenance | Full existing prepare/apply/update/remove/revoke/rebase and retained inspection after provider loss; unsupported target not missing interface | | Build/distribution/publication M-07/M-12 | Artifact DAG/recipes/subjects, checks/smoke policy, prepared effects/authority and partial receipts | Full prepare/validate/authorize/apply/status/recovery; source tests/smoke choices represented; no public write from merely opening an IDE | | Environment/tools/store M-14/M-15 | Target/executor/principal, runtime closure/payload/file ownership, generations/refs/GC candidates and compatibility | HOME apply/exec/update/remove/activate/rollback/verify/GC and full structured partial recovery; separate logical and physical roots | | Linux/image/service M-15 | Backend closure/DB generation, rootfs metadata, image stages/layers, catalog/endpoints/auth and health | Image build/export/load/replacement/rollback; service probe/read/write/refusal; responsive operations, runtime-data boundaries and no-GitHub evidence | | Existing administrative/refactor tools M-17-A/B | Actual command inventory, configuration/source conversion plans, cache/registry/version/tool state and complete typed reference scope | All supported domain operations exposed, including package rename; no shell/TUI-keyscript required for semantic functionality | | Cross-cutting M-16/M-17 | Capability/schema coverage, context/overlay snapshots, typed errors/events, trace/capture availability and retention | Two independent headless clients prove all paths, strict inputs, reconnect/cancel/partial failures and equivalent authority without any IDE/plugin |
04| Domain / owner | Externally inspectable models | Required external actions and closure proof |
|---|---|---|
| Sources/facts/requirements M-01/M-02/M-04 | Classified raw/projection resources, exact locations/proofs, relations/refinements/coverage/closure and diagnostics | Same-snapshot navigation/search/references and buffer-aware analysis; structured scaffold/answer/promote/close and exact stale/partial errors |
| Selection/install M-05 | All root requests, candidates/rejections, options/effects, selected edges/lock, visible-world and freshness reasons | Discover/select/prepare/install/update/reinstall/remove, typed NeedsSelection, reverse-dependency effects, no hidden TTY/default |
| Tree/boot M-06 | Complete package/occurrence graph, visibility provenance, stage carriers, source mapping, costs and preview scenarios | Tree/children/explain/compare/capture/export by snapshot; all text-only provenance becomes structured; no absent≡unreadable/unresolved≡unchecked |
| Lifecycle/change M-03/M-04/M-11 | Request/run/input/output/pre/post transition, parked work, evidence/closure and failure journal | Prepare/run/adopt/observe/control/reconnect/recover under actual workspace limits; repeated request never duplicates production |
| Adapters/extensions/derivatives M-08/M-09/M-10 | Schemas/capabilities/selection, grants, resource ownership, base/local/result and active content provenance | Full existing prepare/apply/update/remove/revoke/rebase and retained inspection after provider loss; unsupported target not missing interface |
| Build/distribution/publication M-07/M-12 | Artifact DAG/recipes/subjects, checks/smoke policy, prepared effects/authority and partial receipts | Full prepare/validate/authorize/apply/status/recovery; source tests/smoke choices represented; no public write from merely opening an IDE |
| Environment/tools/store M-14/M-15 | Target/executor/principal, runtime closure/payload/file ownership, generations/refs/GC candidates and compatibility | HOME apply/exec/update/remove/activate/rollback/verify/GC and full structured partial recovery; separate logical and physical roots |
| Linux/image/service M-15 | Backend closure/DB generation, rootfs metadata, image stages/layers, catalog/endpoints/auth and health | Image build/export/load/replacement/rollback; service probe/read/write/refusal; responsive operations, runtime-data boundaries and no-GitHub evidence |
| Existing administrative/refactor tools M-17-A/B | Actual command inventory, configuration/source conversion plans, cache/registry/version/tool state and complete typed reference scope | All supported domain operations exposed, including package rename; no shell/TUI-keyscript required for semantic functionality |
| Cross-cutting M-16/M-17 | Capability/schema coverage, context/overlay snapshots, typed errors/events, trace/capture availability and retention | Two independent headless clients prove all paths, strict inputs, reconnect/cancel/partial failures and equivalent authority without any IDE/plugin |
05Full path is demonstrated by protocol conformance clients using the same services as CLI/MCP. Required journeys: inspect→unsaved edit→diagnose/preview without disk effects; package rename→review→saved-state apply→regeneration→navigation; admitted long action→disconnect/reconnect/cancel→truthful evidence; extension discovery/revocation→retained inspection; HOME update→Docker rebuild/replacement→authorized/denied service operation, all linked by shared provenance.
06M-16 lays common contracts early. M-17-A completes initial-operation/model exposure before M-12; M-17-B delivers semantic package rename; M-17-C/D closes the full M-15-inclusive external contract. A domain implementation may finish its focused work before final cross-domain tests, but it cannot be called IDE/ETO complete by substituting a stub/unavailable result for a supported capability. A future plugin can be designed after these gates using the actual schemas; no plugin work is scheduled here.