generated from coulomb/repo-seed
Added deterministic function layer
This commit is contained in:
@@ -39,7 +39,7 @@ and descriptions mirror the operational view.
|
||||
| `MKTT-WP-0011` | complete | done | `MKTT-WP-0003`; task-level triggers: `MKTT-WP-0010-T001`, `MKTT-WP-0010-T005` | Markdown dataflow workflow layer is complete: workflow standard, source collectors, binding model, deterministic steps, assisted boundary, safe outputs, CLI, docs, and examples. |
|
||||
| `MKTT-WP-0009` | complete | done | `MKTT-WP-0006` | Access-controlled knowledge gateway is complete: local labels, trust zones, path rules, policy-aware cache query/search, decisions, diagnostics, and external adapter boundaries. |
|
||||
| `MKTT-WP-0014` | complete | done | `MKTT-WP-0009` | Markitect-side enterprise IAM access-control integration is complete: NetKingdom/key-cape-compatible identity claims, flex-auth resource/policy contract, directory group resolution fixtures, decision-log sink, workflow declarations, CLI commands, and external PDP request examples. |
|
||||
| `MKTT-WP-0012` | P3 | todo | `MKTT-WP-0004`, `MKTT-WP-0010`, `MKTT-WP-0011` | Future Quarkdown-inspired document function layer: reusable Markdown-native function calls over processors, references, contracts, workflows, and later assisted steps. |
|
||||
| `MKTT-WP-0012` | complete | done | `MKTT-WP-0004`, `MKTT-WP-0010`, `MKTT-WP-0011` | Document function layer is complete: deterministic Markdown-native function descriptors, registry, inline/fenced syntax, pipelines, context bindings, CLI, docs, examples, diagnostics, provenance, and extension descriptor. |
|
||||
| `MKTT-WP-0008` | P3 | todo | `MKTT-WP-0006`, `MKTT-WP-0007`, `MKTT-WP-0009` | Agent working-memory cache after backend and policy floor are available. |
|
||||
|
||||
## Dependency Notes
|
||||
@@ -69,11 +69,10 @@ runtime/workflow expansion because it reduces central wiring and gives future
|
||||
features a canonical processing context/result/diagnostic/provenance model. It
|
||||
is not a business dataflow layer; that remains `MKTT-WP-0011`.
|
||||
|
||||
`MKTT-WP-0012` captures the Quarkdown-inspired document function layer. It
|
||||
should follow `MKTT-WP-0011` because the workflow layer will reveal which
|
||||
operations deserve author-facing function syntax. It should remain optional and
|
||||
capability-gated, especially before assisted, external, file, or network
|
||||
functions are allowed.
|
||||
`MKTT-WP-0012` completed the Quarkdown-inspired document function layer as a
|
||||
deterministic authoring surface over existing Markitect capabilities. Assisted,
|
||||
external, file, network, render/export, and provider-backed functions remain
|
||||
future optional extensions behind local capability and policy gates.
|
||||
|
||||
`MKTT-WP-0014` completed Markitect-side enterprise IAM integration for the
|
||||
access-control gateway. Central authorization administration remains optional
|
||||
|
||||
Reference in New Issue
Block a user