You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<imgsrc="assets/brand/comptext-cli-readme-header.jpg"alt="CompText CLI — CLI Runtime for Deterministic Context"width="100%">
2
+
<imgsrc="assets/brand/comptext-cli-readme-header.jpg"alt="CompText CLI - CLI Runtime for Deterministic Context"width="100%">
3
3
</p>
4
+
4
5
<divalign="center">
5
6
6
7
# CompText `ctxt`
7
8
8
-
**Deterministic contract runtime for agent-friendly local review workflows.**
9
+
**Deterministic local CLI runtime for agent-readable JSON contracts.**
9
10
10
11
**Models are providers. Context is the product.**
11
12
@@ -26,147 +27,114 @@ It does not execute external agents, use network, call providers, apply proposal
26
27
27
28
</div>
28
29
29
-
CompText `ctxt` v0.1.0 is a local-first Rust CLI for deterministic, schema-oriented review workflow contracts. It gives Codex, Antigravity, and human reviewers stable JSON entrypoints for startup checks, capability discovery, proposal evidence, review evidence, subagent role contracts, and validation summaries before any higher-risk action is considered.
30
+
> **Safety boundary**
31
+
>
32
+
> `ctxt` is local-first. Network is denied by default. Provider calls are not part of the documented workflow. External agent execution is disabled. Proposal and review artifacts are evidence, not instructions to auto-apply. Subagent role contracts are available, but subagents do not execute. No MCP server implementation is claimed.
30
33
31
-
The current release candidate is focused on contract clarity, local evidence, and safe startup behavior. It is not an autonomous coding system, not a provider gateway, and not a remote orchestration layer.
34
+
CompText `ctxt` v0.1.0 is a release candidate until the release is tagged.
Most agent workflows start with ambiguous state and only later discover whether the environment was safe, validated, or consistent. CompText flips that order:
54
+
**What it is:**`ctxt` is a Rust CLI that emits deterministic JSON contracts for local agent and reviewer workflows.
52
55
53
-
1. expose local runtime contracts first,
54
-
2. report capabilities before actions,
55
-
3. keep artifacts bounded and inspectable,
56
-
4. make disabled gates explicit,
57
-
5. validate locally before claims,
58
-
6. summarize evidence for the user.
56
+
**Why it exists:** agent sessions need a reliable way to inspect startup state, supported commands, disabled gates, local artifacts, and validation evidence before making claims or attempting higher-risk work.
59
57
60
-
The result is a small CLI surface that helps an agent or reviewer answer: what is available, what is disabled, what evidence exists, and what local validation says.
58
+
**Who uses it:** humans, Codex, Antigravity, and other local automation can call the same `ctxt --json ...` entrypoints to read the project contract surface without widening permissions.
61
59
62
-
## Architecture
60
+
The product is the context boundary: stable inputs, explicit gates, bounded artifacts, and local validation before provider interaction is considered.
63
61
64
-
```mermaid
65
-
flowchart LR
66
-
user["User or Agent"] --> cli["ctxt CLI"]
67
-
cli --> contracts["JSON contracts"]
68
-
contracts --> artifacts["Local artifacts"]
69
-
contracts --> validation["Validation output"]
70
-
artifacts --> summary["User summary"]
71
-
validation --> summary
72
-
```
62
+
## Install / Run
73
63
74
-
`ctxt` is intentionally boring at the boundary: commands produce local JSON contracts and evidence-oriented output. That makes it easier for automation to inspect state without assuming permission to mutate files, call providers, or reach the network.
The review workflow is a contract-only checklist. Each command is run explicitly by the user or agent inside the allowed task scope. The workflow does not imply remote execution, hidden automation, or automatic application of recommendations.
`ctxt` gives Codex, Antigravity, and human reviewers a shared local contract surface. It is an adapter-friendly runtime boundary, not a remote orchestration layer.
93
+
94
+
Before edits:
131
95
132
96
```powershell
133
-
cargo run --bin ctxt -- --json self report
134
97
cargo run --bin ctxt -- --json startup readiness
135
-
cargo run --bin ctxt -- --json startup flow
98
+
cargo run --bin ctxt -- --json capabilities
136
99
cargo run --bin ctxt -- --json review workflow
100
+
```
101
+
102
+
After edits:
103
+
104
+
```powershell
137
105
cargo run --bin ctxt -- --json validate --run
138
106
```
139
107
140
-
All commands are local CLI invocations. The documented review workflow does not enable network access, provider calls, external agent execution, proposal application, review application, or subagent execution.
108
+
The commands above are local CLI invocations. They do not enable provider calls, network access, external agent execution, proposal application, review application, or subagent runtime execution.
contracts --> startup["Startup and capability state"]
168
+
contracts --> evidence["Local artifacts and bounded reads"]
169
+
contracts --> validation["Validation output"]
170
+
startup --> summary["User summary"]
171
+
evidence --> summary
172
+
validation --> summary
173
+
```
174
+
175
+
`ctxt` keeps the first interaction local and deterministic. Callers ask the runtime what is supported, what is disabled, what evidence exists, and what validation says.
capabilities --> subagents["subagent role contracts"]
185
+
subagents --> proposals["proposal artifacts"]
186
+
proposals --> reviews["review artifacts"]
187
+
reviews --> workflow["review workflow"]
188
+
workflow --> validate["validate --run"]
189
+
validate --> summary["user summary"]
190
+
```
191
+
192
+
The review workflow is a checklist contract. It does not run hidden automation, invoke external agents, call providers, apply artifacts, or change Git state.
189
193
190
194
## Safety Matrix
191
195
192
-
| Boundary | Default |Rationale|
196
+
| Boundary | Default |README R2 wording|
193
197
|---|---|---|
194
-
| Network | Denied | Local evidence and deterministic contracts come first |
195
-
| Provider calls | Denied | Providers are not needed for contract inspection |
196
-
| External agents | Denied | Discovery is metadata, not execution |
| Subagent runtime execution | Disabled | Subagent role contracts are available only as definitions |
204
+
| MCP server | Not implemented | No MCP server implementation claim |
205
+
| Provider gateway | Not implemented | No provider gateway claim |
206
+
| Hooks and plugins | Disabled for this flow | Not required for release-candidate validation |
207
+
| Arbitrary shell | Out of scope | Use declared local validation commands |
208
+
| Secrets | Never read or printed | Secret material must not enter artifacts or reports |
204
209
| Git writes | User-authorized only | Commit, push, tag, and release require explicit instruction |
205
210
206
211
## Validation Evidence
@@ -217,7 +222,7 @@ unit tests: 38 green
217
222
smoke tests: 83 green
218
223
```
219
224
220
-
Recommended local validation before reporting success:
225
+
Recommended local validation:
221
226
222
227
```powershell
223
228
cargo fmt --all --check
@@ -227,47 +232,63 @@ cargo clippy -- -D warnings
227
232
cargo run --bin ctxt -- --json validate --run
228
233
```
229
234
230
-
## Visual Asset Plan
235
+
For README-only edits, the minimum documentation check is:
231
236
232
-
README diagrams stay as Mermaid so they remain version-controlled, reviewable, and rendered directly by GitHub.
237
+
```powershell
238
+
git --no-pager diff -- README.md
239
+
git --no-pager status --short --branch
240
+
```
233
241
234
-
Figma can be used later for a GitHub README header, social preview card, footer strip, architecture poster, and launch image. Generated asset references should not be added unless matching files already exist in the repository and the active task explicitly allows them.
242
+
## Distribution / Release Channel
235
243
236
-
## Roadmap
244
+
v0.1.0 is currently a release candidate. The source workflow is the supported path until the release is tagged and the crate publication decision is made.
245
+
246
+
Release actions that remain separate from this README:
237
247
238
-
The active project source of truth is `PROJEKT.md`, and concrete work slices live in `tasks/*.md`.
248
+
- tag creation,
249
+
- GitHub Release creation,
250
+
- crate publication,
251
+
- cargo-dist initialization,
252
+
- social preview setup.
253
+
254
+
Do not infer that any of those actions have happened from this README.
255
+
256
+
## Roadmap
239
257
240
258
Near-term release-candidate priorities:
241
259
242
-
- keep READMEand task state aligned with Phase 5e,
260
+
- keep README, release notes, and project state aligned,
243
261
- preserve deterministic JSON contract behavior,
244
262
- keep local validation green,
245
-
- improve community-facing examples without widening runtime permissions,
246
-
- add visual assets only in a dedicated visual-assets task.
263
+
- document Codex and Antigravity usage through `ctxt`,
264
+
- keep binary and media assets outside context packing,
265
+
- decide release tag and distribution channel only after CI is green.
266
+
267
+
Later work may expand installation paths, packaging, and visual launch assets without changing the core local-first boundary.
247
268
248
269
## Contributing
249
270
250
-
Contributions should preserve the core safety model:
271
+
Contributions should preserve the project contract:
251
272
252
-
- deterministic contracts before provider interaction,
273
+
- deterministic Context Packs before provider interaction,
253
274
- dry-run before network,
254
275
- proposal before apply,
255
276
- model, provider, and tool output treated as untrusted input,
256
277
- local validation before success claims,
257
278
- no secrets in stdout, stderr, reports, context packs, proposals, snapshots, logs, or generated artifacts.
258
279
259
-
For README/community work, stay inside the declared task scope and validate with:
280
+
Use the same startup checks before changing behavior:
260
281
261
282
```powershell
262
-
git --no-pager diff -- README.md
263
-
git --no-pager status --short --branch
283
+
cargo run --bin ctxt -- --json startup readiness
284
+
cargo run --bin ctxt -- --json capabilities
285
+
cargo run --bin ctxt -- --json review workflow
264
286
```
265
287
266
288
## License
267
289
268
290
MIT.
291
+
269
292
<palign="center">
270
-
<imgsrc="assets/brand/comptext-cli-readme-footer.jpg"alt="CompText CLI — Compress the noise. Preserve the proof."width="100%">
293
+
<imgsrc="assets/brand/comptext-cli-readme-footer.jpg"alt="CompText CLI - Compress the noise. Preserve the proof."width="100%">
0 commit comments