Repository navigation
Offline initiative explorer
executor views writes one self-contained HTML page per initiative
(.executor/<INIT>/views/index.html) plus a parent index of every initiative in
the store (.executor/views/index.html). Each page carries an overview, a
dependency graph, an entity graph, tables for tasks, dispatches, evidence,
decisions and artifacts, a daily timeline, an inspector, and a command palette.
- Browser libraries are vendored under
engine/executor/web/vendor/— Preact
10.29.8, htm 3.1.1, D3 7.9.2, MiniSearch 7.2.0 — with licenses and a SHA-256
manifest. A changed or unlisted file stops the build. - Pages make no network requests. The Content-Security-Policy admits only each
page's own inline script and style, by hash. - The store's version verdict (current / migration needed / newer executor
needed) appears on both pages.
Branch gates
The hierarchy the skill documented is now enforced by the engine:
- Implementation dispatches start from the tip of
plan/<PLAN-ID>, not from
whatever branch is checked out —missing_plan_branch. - Plan merges must name
initiative/<INIT-ID>—merge_branch_mismatch. - Implementation is refused until the plan's documents are committed on the
initiative branch (projections_uncommitted,initiative_branch_missing). - The dispatch base must carry every dependency head already reported —
dependency_not_contained. - Handoff is refused while any plan is unmerged or absent from the initiative
branch —integration_incomplete. - New dispatches carry
rules: v3; reports are judged under any supported rules
version, so upgrading never drops checks for work in flight.
Packaging
The skill bundle ships Python only. The explorer's browser assets stay in the
source tree, and a bundled executor views writes the markdown views alone.
Verification
929 tests pass with 100% branch coverage of engine/executor and scripts;
bundle drift check and skill validation are clean.