Markitect boundary and reuse tests
This commit is contained in:
parent
9f1b8da87a
commit
ef8391e6a7
15 changed files with 490 additions and 6 deletions
|
|
@ -38,6 +38,14 @@ Implement the service API as an adapter over application services, following
|
|||
Agent operations must use the bounded operation catalog, policy checks, audit
|
||||
events, dry-run behavior, and review gates described in the blueprint.
|
||||
|
||||
## markitect-tool Boundary Remark
|
||||
|
||||
Service and agent APIs may expose engine operations that internally use
|
||||
Markitect for markdown-backed context packages, selectors, validation, and
|
||||
deterministic markdown operations. They must not expose the `mkt` CLI as the
|
||||
engine control plane or let agents bypass engine policy, audit, lifecycle, and
|
||||
review gates through Markitect APIs.
|
||||
|
||||
## S9.1 - Implement versioned FastAPI service skeleton and health contracts
|
||||
|
||||
```task
|
||||
|
|
@ -151,6 +159,8 @@ Acceptance:
|
|||
- Package contents are source-grounded and permission filtered.
|
||||
- External memory references remain opaque and respect
|
||||
`docs/phase-memory-boundary.md`.
|
||||
- Markdown-backed packages can interoperate with Markitect context-package
|
||||
payloads while remaining wrapped in engine permission and audit contracts.
|
||||
|
||||
## S9.7 - Implement dry-run review-gate and contract-test coverage
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue