Contract robustness and bottleneck test
This commit is contained in:
parent
ef8391e6a7
commit
fcd50bdfe8
14 changed files with 654 additions and 79 deletions
|
|
@ -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.
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue