Context before decisions

When context changes,
what needs a second look?

PrincipalLoop ties a proposal to the facts, files and hypotheses behind it — so you can continue with confidence, or know exactly why to stop.

Verifiable snapshotsSynthetic data · No model

scenarios executedincluding one visible limit

objects in the capturewith revisions and provenance

file keptbytes and SHA-256 fingerprint

Explore the scenarios

Same proposal. Different contexts.

Eight scenarios executed by the kernel. No model, no personal data.

Reading without JavaScript

Everything is consistent — The premises read and the captured file are unchanged. The context still supports reviewing the proposal.

An unrelated event — Another task moves forward. The journal advances, but none of the proposal's dependencies changed.

A replaced hypothesis — The idempotency hypothesis was replaced. A proposal built on its first revision must be reviewed again.

The code changed — The file keeps the same name, yet its content differs from what was captured and checked.

An unstable capture — The file changed between the two capture reads. The bytes are kept, with an explicit unstable status.

An undeclared read — The director read a second hypothesis, then left it out of its proposal. The recorded read still reveals the change.

A mandatory dependency — A dependency imposed by the operator changed. Leaving it out of the proposal does not exempt it from the check.

The limit to know — A relevant dependency was neither declared, served nor imposed. The check cannot find it: admissible context is not proof of completeness.

Exploring contents and dependencies requires JavaScript, which runs only inside this local file.

Capture reportFrozen report · No live monitoring

Why this result?

Checked dependencies

This verdict is about context freshness. It authorizes no action and does not prove that a director is useful.

Inside the snapshot

Filter the context

References and traceability

A measurable promise

Show what holds.
Make the limits visible.

These checks are about context, not about whether a director is useful.
A dependency that was never observed can stay invisible.
A double read detects changes; it does not lock the file system.

Replay this demo

One command runs the eight scenarios and opens this standalone report.

principalloop demo

The Codex plugin keeps and compares context. The autonomous director is still to be built; its strategic benefit is not established yet.