Turn a source fragment into explicit work, inspect a proposed graph addition, and commit its evidence record. This local SQLite kernel separates source, task packet, candidate, checkpoint result and accepted graph so a generated claim does not silently become stored truth.
It is a generic source snapshot from a larger atlas experiment. The private atlas and domain data are excluded; Research Notes is a synthetic public pack. Origin
Python 3.11+, from this checkout:
python -m pip install -e .
python -m atlas_kernel.walkthrough
python -m atlas_kernel.demo
python -m pip install pytest
python -m pytest -qThe new walkthrough uses a temporary database and prints a complete stable trace:
- Store the source “18 of 20 checks” and its hash.
- Generate a research-claim packet with an evidence-link checkpoint.
- Reject a proposed 90-percent finding with no evidence edge; no graph/commit rows are added.
- Submit a separate candidate with a
derived_fromedge and commit it. - Observe that the packet is still in progress, then explicitly mark it complete.
The old end-to-end demo also prints health, Mermaid and text-tree views. Both examples clean their disposable databases. The synthetic pack is included in the distribution: atlas-demo and python -m atlas_kernel.walkthrough also work after installation outside the checkout.
| Boundary | Source |
|---|---|
| Pack files → registered types and seed graph | pack_loader.py |
| Source + detected type → persisted task packet | packet_engine.py |
| Proposed nodes/edges → checkpoint verdict | commit_engine.py |
| Accepted candidate → nodes, edges, commit record and candidate status | Same commit engine, one database transaction |
| Packet completion | Separate explicit mark_completed operation |
| Inspect graph | render_engine.py and repository.py |
The walkthrough is also a consumer recipe: initialize the database, construct registry/repository, load the packaged domain, then use PacketEngine and CommitEngine. It contains no hidden worker or provider.
Copy the Research Notes pack, adjust its manifest and types, and follow the authoring contract. Validate with atlas-validate-pack YOUR_PACK_DIRECTORY before loading. Atlas Domain Pack SDK offers the authoring validator without the runtime database; its distinct command can coexist with this package.
Procedures and lenses describe intended work; they do not cause an autonomous worker to run. New condition names require an implemented checkpoint handler. Required checkpoint references must resolve even if the checkpoint file is missing or empty.
The included evidence checkpoint checks that at least one proposed edge has type derived_from. It does not prove the edge supports every finding, its target is the right source, or the arithmetic/text is correct. Confidence is supplied by the candidate. The example's 90 percent is authored locally; no model is evaluated.
A successful commit's graph rows, commit record and candidate status are transactional. Packet completion is separate. Existing node IDs update status/time rather than replacing all node properties; treat these examples as additions, not a general graph edit API. Pack loading is not a migration/version-upgrade service.
The next valuable extension would verify every claimed evidence target and define update semantics before adding more automated workers.