Repository navigation
feat(applications): add read-only maintainer context CLI #229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
d6c91e6
71ac8e3
b05f22d
39ad4d2
b83cdab
3cbfda7
18a75b3
06616f8
930b4f4
db540ec
4b72057
5b511e8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -177,9 +177,13 @@ non-File providers remain `NOT_ACTIVE`; see | |
| [ADR-0068](./docs/decisions/0068-activate-loopback-dogfood-runtime.md). | ||
|
|
||
| Once the bounded API is running, the maintainer caller and Quality runner are | ||
| documented in [`eval/README.md`](./eval/README.md). They call only the frozen | ||
| resolve HTTP operation; the evaluation report remains separate from the | ||
| security release gate. | ||
| separate surfaces. Use the read-only | ||
| [`context-engine-context`](./docs/operations/maintainer-context-cli.md) CLI for | ||
| fresh questions and untrusted Package inspection. Evaluation replay remains in | ||
| [`eval/README.md`](./eval/README.md). Both callers use only the frozen resolve | ||
| HTTP operation; the maintainer CLI has no Control, ActionPlane, model, or | ||
| promotion authority, and evaluation remains separate from the security release | ||
| gate. | ||
|
|
||
| ### Run the worker | ||
|
|
||
|
|
@@ -519,7 +523,7 @@ engine/ The sealed core — no HTTP, no vendor SDKs | |
| adapters/ Everything that touches the outside world | ||
| http/ FastAPI ingress, authentication, transport limits, routes | ||
| parsers/ format parsers (PDF / Markdown / Office) | ||
| applications/ Thin process entry points (~200 LOC total) | ||
| applications/ Thin process entry points and operator CLIs — wiring only | ||
| api.py `context-engine-api` | ||
| worker.py `context-engine-worker` | ||
| bot_delivery/ M2 trusted Bot process (TypeScript); generated-SDK caller | ||
|
|
@@ -535,13 +539,14 @@ PLAN.md vision, principles, roadmap, non-goals | |
|
|
||
| Two structural facts worth noticing: | ||
|
|
||
| - **Thin entry points, thick core.** `applications/` is roughly 200 lines. All | ||
| behavior lives in `engine/`, which is what makes "the production composition | ||
| root cannot substitute, skip, or wire a no-op `AuthorizationKernel`" an | ||
| enforceable property rather than a slogan. | ||
| - **Tests outweigh implementation ~3:1.** Roughly 21k lines under `engine/` | ||
| against roughly 68k lines under `tests/`. For a project whose central claim is | ||
| a security invariant, the executable evidence *is* the product. | ||
| - **Thin entry points, thick core.** Every module in `applications/` only parses | ||
| arguments and wires a composition; no authorization, retrieval, or delivery | ||
| behavior lives there. All of it lives in `engine/`, which is what makes "the | ||
| production composition root cannot substitute, skip, or wire a no-op | ||
| `AuthorizationKernel`" an enforceable property rather than a slogan. | ||
| - **Tests outweigh implementation ~3:1.** The `tests/` tree is several times the | ||
| size of `engine/`. For a project whose central claim is a security invariant, | ||
| the executable evidence *is* the product. | ||
|
Comment on lines
+547
to
+549
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win Remove the numeric repository-size claim from both READMEs. Both changed sections retain an approximate
📍 Affects 2 files
🤖 Prompt for AI Agents |
||
|
|
||
| ### What is pluggable, and what is not | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.