I learn more from a complete technical workflow than from a feature reel.
A complete workflow shows the input, the command or interface, the intermediate state, the usable output, and the condition that limits the claim. It also leaves enough material behind for another person to inspect the run.
I applied that standard to four public Project Telos tools: Index, Gather, Forum, and Crucible. The resulting recorded-workflow hub contains short cuts, full recordings, commands, evidence packages, and an explicit boundary for every demo.
Here is what each workflow actually establishes.
1. Index: map a workspace, then check the map
Index 2.9.0 scans a sanitized workspace with three repositories. The captured run produces three high-confidence dependency edges and records the file-and-line witness behind each one.
The workflow then checks one dependency directly, returning MATCH for the edge from operator-console to routing-service at pyproject.toml:5. It also builds a bounded context result: 738 of 1,200 tokens, all three repositories retained, zero omitted. The final artifact is an offline atlas.
The fixture is deliberately small enough to inspect by hand. It proves the mapping, evidence, bounded-context, and workbench path. It is not a scale benchmark or a claim of complete language coverage. The run uses no model and no network.
2. Gather: keep the receipt with the research
Gather 1.6.1 converts local source material into addressable, content-hashed blocks. The demo extracts seven structured blocks, stores two records in a local corpus, and re-reads both stored bodies against their provenance records.
The initial verification returns 2/2 MATCH. The workflow then changes a receipt and runs the check again, exposing the tamper path instead of hiding it.
The useful design property is straightforward: recall and verification operate on the stored material, not on a retrospective claim that the material is unchanged.
3. Forum: preserve causal structure across dependent work
Forum 1.13.0 routes one cross-domain backend-and-documentation request into three dependent waves. Upstream results cross typed data edges into downstream tasks. Each wave closes with a checkpoint, and each task result passes its validator.
The captured run leaves 19 ledger entries and three checkpoints. The final checks verify the hash chain and the content-addressed payload bodies.
This workflow uses a disclosed deterministic offline model fixture. That makes the orchestration and evidence mechanics reproducible. It does not measure production-model quality, latency, or cost.
4. Crucible: hold the criterion still
Crucible 1.2.0 evaluates a three-claim artifact. The first run returns 1 MATCH / 2 DRIFT. The artifact is refined while the criterion stays fixed, and the second run returns 3 MATCH / 0 DRIFT.
Two cleanroom reviews pass. The final step re-derives the verdict from the artifacts on disk.
Keeping the criterion fixed matters. Without that constraint, a workflow can make a result look better simply by weakening the test after seeing the failure.
What these demos do not claim
The four tools have distinct jobs and distinct fixtures. The recordings do not pretend that they form one zero-touch production pipeline. They do not substitute fixture results for production-model benchmarks. They do not turn a three-repository map into a scale claim.
That honesty makes the useful connection clearer:
- Context must be current enough to act on.
- Research material must retain its acquisition and integrity record.
- Dependent work must retain its causal structure.
- Evaluation must hold its criterion still and expose failure.
When those properties survive a handoff, a completed run becomes part of the capability environment for the run that follows. A map can become onboarding material. A research record can become a test fixture. A dependency plan can become a benchmark. A failed evaluation can sharpen the criterion.
That is the practical meaning of capability compounding.
I am open to paid engineering, applied research, technical writing, contract, and collaborative work across developer tools, AI infrastructure, compilers, graphics, color systems, and technical products.
Open the workflow hub, choose one run, and tell me which boundary deserves the hardest test.
Top comments (0)