generated from coulomb/repo-seed
Contract robustness and bottleneck test
This commit is contained in:
@@ -0,0 +1,33 @@
|
||||
---
|
||||
document_type: adr
|
||||
status: accepted
|
||||
owner: Platform Knowledge
|
||||
tags:
|
||||
- context
|
||||
- markdown
|
||||
- governance
|
||||
policy:
|
||||
labels: [public, engineering]
|
||||
source:
|
||||
system: repo
|
||||
path: examples/markitect-tool-contract/corpus/adr-0001-context-packages.md
|
||||
---
|
||||
|
||||
# Use Markitect Context Packages
|
||||
|
||||
## Context
|
||||
|
||||
The problem is that the engine needs Markdown-native structure and context
|
||||
packages without owning a second Markdown parser or selector language.
|
||||
|
||||
## Decision
|
||||
|
||||
We will use markitect-tool as the Markdown syntax, selector, deterministic
|
||||
operation, snapshot, and context-package layer for Markdown-backed assets.
|
||||
|
||||
## Consequences
|
||||
|
||||
- Engine assets stay cross-format and durable.
|
||||
- Markdown selectors stay Markitect-owned.
|
||||
- Adapter provenance can be stored with engine transformation runs.
|
||||
|
||||
@@ -0,0 +1,18 @@
|
||||
---
|
||||
document_type: adr
|
||||
status: accepted
|
||||
owner: Platform Knowledge
|
||||
policy:
|
||||
labels: [public, engineering]
|
||||
---
|
||||
|
||||
# Weak Decision Record
|
||||
|
||||
## Context
|
||||
|
||||
The note mentions a need but does not contain the required decision section.
|
||||
|
||||
## Deprecated Approach
|
||||
|
||||
This forbidden section should be reported by the Markitect contract checker.
|
||||
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
document_type: policy
|
||||
status: active
|
||||
owner: Platform Knowledge
|
||||
policy:
|
||||
labels: [public, governance]
|
||||
source:
|
||||
system: repo
|
||||
path: examples/markitect-tool-contract/corpus/engineering-policy.md
|
||||
---
|
||||
|
||||
# Engineering Knowledge Policy
|
||||
|
||||
## Controls
|
||||
|
||||
Published context packages must preserve source paths, source spans, policy
|
||||
labels, and enough provenance for the engine to audit how the package was
|
||||
assembled.
|
||||
|
||||
## Review
|
||||
|
||||
Sensitive or high-impact generated artifacts must pass through an engine-owned
|
||||
review gate before publication or export.
|
||||
|
||||
@@ -0,0 +1,22 @@
|
||||
---
|
||||
document_type: risk-note
|
||||
status: draft
|
||||
owner: Platform Knowledge
|
||||
policy:
|
||||
labels: [internal]
|
||||
source:
|
||||
system: repo
|
||||
path: examples/markitect-tool-contract/corpus/internal-risk-note.md
|
||||
---
|
||||
|
||||
# Internal Retrieval Risk
|
||||
|
||||
## Risk
|
||||
|
||||
This internal note should not appear in a public context activation.
|
||||
|
||||
## Mitigation
|
||||
|
||||
Permission filtering must happen before snippets, context packages, or derived
|
||||
outputs are returned to a caller.
|
||||
|
||||
Reference in New Issue
Block a user