CompText

The Operating System for Context
Deterministic context infrastructure for AI systems.

Models are providers. Context is the product.
Deterministic. Portable. Verifiable.

Quickstart · Why CompText? · Artifacts · Contributing · Brand Assets · Skill Registry

CompText CLI (ctxt) is an experimental, local-first terminal tool for turning messy repository state into deterministic, reviewable Context Packs before talking to model providers.

It helps you keep AI-assisted development grounded in artifacts: context packs, request files, proposal JSON, validation output, benchmark records, and phase reports.

CompText is not a blind autonomous coding agent. It is a proposal-gated workflow for safer, more inspectable engineering.

---

Why CompText?

Most AI coding workflows start by sending a lot of vague context to a model and then trusting the conversation.

CompText takes a different path:

1. inspect the repository,
2. build a deterministic Context Pack,
3. pass through explicit policy gates,
4. treat provider output as untrusted,
5. write proposals instead of mutating files immediately,
6. apply only reviewed changes,
7. validate locally,
8. preserve evidence as artifacts.

flowchart TD
    A[Repository] --> B[Context Pack]
    B --> C[Policy Gate]
    C --> D[Provider Boundary]
    D --> E[Untrusted Response]
    E --> F[Proposal Artifact]
    F --> G{Review}
    G -->|approve| H[Apply Gate]
    G -->|reject| I[Stop]
    H --> J[Local Validation]
    J --> K[Report / Benchmark / Evidence]

Loading

The goal is simple:

Less noisy context. More verifiable proof.

---

Who is this for?

CompText is for developers who want AI-assisted workflows with stronger boundaries:

• Rust / CLI developers experimenting with local-first agent tooling
• prompt engineers building repeatable context workflows
• AI agent developers who care about policy gates and evidence artifacts
• teams exploring provider-agnostic coding workflows
• reviewers who want to see what changed, why, and how it was validated

---

Current Status

Binary: ctxt
Current phase: Phase 17
Current task: Antigravity Plugin Bundle Skeleton
Last green phase: Phase 16
Status: REVIEW-GATE
Next allowed action: Await review gate confirmation

Completed so far:

Phase 0   Repo Genesis & Bootstrap              COMPLETE
Phase 1   CLI Shell Hardening                    COMPLETE
Phase 2   Context Pack Contract                  COMPLETE
Phase 3   Provider Adapter Layer / Dummy         COMPLETE
Phase 4   Ollama Local Adapter                   COMPLETE
Phase 4B  Skill Registry Normalization           COMPLETE
Phase 4C  Long-Run Autonomy Hardening            COMPLETE
Phase 5   Proposal Mode                          COMPLETE
Phase 6   Apply Gate                             COMPLETE
Phase 7   Provider Config Layer                  COMPLETE
Phase 8   OpenAI-Compatible Adapter              COMPLETE
Phase 9   Validate and Benchmark                 COMPLETE
Phase 10  MVP Stabilization & Release Readiness  COMPLETE
Phase 11  Release Packaging                      COMPLETE
Phase 12  Antigravity CLI Governance & Token Economy COMPLETE
Phase 13  Skill Bundle Registry                  COMPLETE
Phase 14  Hook/Permission Integration            COMPLETE
Phase 15  Cryptographic Provenance Engine        COMPLETE
Phase 16  Agent State Contract Skeleton          COMPLETE
Phase 17  Antigravity Plugin Bundle Skeleton     REVIEW-GATE

Next areas:

Phase 18  TBD

Review-Gate Operating Rules

No NEXT without Review-Gate.
No roadmap completion claim while any phase is blocked.
No automatic phase progression.
Review-Gate decides PASS / PASS WITH NOTES / BLOCKED.

Operating modes:

AUDIT           read-only contradiction search
CONSOLIDATE     align README / PROJEKT / reports / docs
FIX             narrow code or documentation repair
REVIEW-GATE     no edits, PASS or BLOCKED only
PHASE WORK      bounded implementation after Review-Gate approval

Current Phase 16 boundaries:

local agent-state capture/verify/report only
agent-state JSON as bounded evidence artifact
sensitive paths skipped or rejected before reads
evidence entries sorted by id and file_path before write
no unsupported assurance claims
no automatic phase progression

flowchart LR
    P5[Proposal Mode] --> P6[Apply Gate]
    P6 --> P7[Provider Config]
    P7 --> P8[OpenAI-Compatible]
    P8 --> P9[Validate + Benchmark]
    P9 --> P10[Stabilization]
    P10 --> P11[Release Package]
    P11 --> P12[CLI Governance]
    P12 --> P13[Skill Registry]
    P13 --> P14[Hook Integration]
    P14 --> P15[Provenance Engine]
    P15 --> P16[Agent State Contract]
    P16 --> P17[Antigravity Plugin Bundle]

Loading

---

Quickstart

1. Clone and build

git clone https://github.com/ProfRandom92/comptext-cli.git
cd comptext-cli
cargo check

2. Run basic checks

cargo fmt --all --check
cargo test
cargo clippy -- -D warnings

3. Try the CLI

cargo run --bin ctxt -- --help
cargo run --bin ctxt -- doctor
cargo run --bin ctxt -- providers list
cargo run --bin ctxt -- version

4. Build context artifacts

cargo run --bin ctxt -- context inspect
cargo run --bin ctxt -- context pack --task "Explain this repository"

5. Run safe model workflows

cargo run --bin ctxt -- ask --dry-run "What is the next safe step?"
cargo run --bin ctxt -- ask --provider dummy "How should I test this repo?"
cargo run --bin ctxt -- propose --provider dummy "Add context inspect"