Skip to content

Latest commit

 

History

History
52 lines (32 loc) · 4.46 KB

File metadata and controls

52 lines (32 loc) · 4.46 KB

Current Development State

This is the canonical record of where Entarium stands. Read it first; it is the only place that answers "what now?"

Updated: 2026-08-13 · Repository context: Entarium 1.0.1 is the current publication (publication-closeout of 1.0.0; runtime and public API unchanged). Development is complete and currently inactive. dist/ is ignored by git and last held gated 1.0.0 artifacts; rebuild for 1.0.1 with scripts/release.py at tag/release time. The v1-proof application is a separate repository and is not part of this one. Package-index publishing remains owner-deferred (MANUAL-REACTIVATION-ONLY). Phase 11 / W-0121 were never committed and are removed rather than kept as history. Packaged consumer materials under vendor/ are publication artifacts for derivative-project use; see docs/consumer-packet.md.

Phase P10 — The v1 declaration (complete)
Milestone P10-M2 — Decided (complete)
Current work item none
Status complete — Entarium 1.0.1 is the current release; no ratchet item is eligible
Last completed W-0120 — The v1 declaration (P10 complete; 1.0.0 declared)
Next after this none — future development requires explicit new owner direction
Blockers none
Validation uv run --frozen --offline python scripts/check.py — run before and after your change. uv sync first if the environment is not provisioned. Green at W-0120 close: 1527 tests passing. Separable, all green when last run: uv run --frozen --offline python scripts/release.py (gated 1.0.0); uv run --frozen --offline python scripts/consumer_smoke.py; uv run --frozen --offline python scripts/panel_consumer.py (needs the sibling ../panel); uv run --frozen --offline python scripts/cross_domain_entity.py; uv run --frozen --offline python scripts/measure_performance.py.

Why there is no next item

W-0120 declared 1.0.0 on W-0119's evidence. The current publication is 1.0.1 (documentation and consumer-packet closeout; runtime unchanged). Entarium is complete and usable now by derivative projects: install a gated wheel or sdist from scripts/release.py, or depend on a git/path reference. Local consumption does not depend on a public package index.

Package-index / public publishing is fit (ADR 0059: the artifact and documentation earn distribution) and intentionally deferred by owner decision. It is recorded in docs/development/backlog.md as MANUAL-REACTIVATION-ONLY: not eligible for automatic promotion, selection, or execution by the standard continuation ratchet. It becomes active only after an explicit future user instruction to pursue publishing.

A continuation session that finds Current work item: none stops and reports. It does not invent a next phase, promote MANUAL-REACTIVATION-ONLY backlog, or select forcing-function candidates on its own.

What earlier items established, so it is not re-litigated:

  • v1 is declared. The census promise is ADR 0052; the changelog states what the number does and does not commit to.
  • Artifacts are already gated. scripts/release.py produces byte-identical wheel and sdist and gates them.
  • W-0119's friction stays in backlog. None of it is a prerequisite for further work without owner direction.

Required reading for this item

There is no current work item. Do not open a phase file to invent one.

Open blockers and decisions

None blocking. There is also nothing scheduled.

W-0112 (authoritative-state snapshot identity) stays elaborated, deferred, and unscheduled.

Deferred discoveries

docs/development/backlog.md — W-0119's four friction entries remain. Package-index publishing is MANUAL-REACTIVATION-ONLY there. Nothing in the backlog is eligible for automatic ratchet selection.

Recent history

docs/development/log.md — owner deferred publishing after W-0120 (Phase 11 / W-0121 removed); W-0120 declared 1.0.0; W-0119 second v1 proof; W-0111 Phase 9 exit review refused v1; W-0118 licence / ADR 0058; W-0116 delivered exposures / ADR 0057.


How to update this file. A session rewrites it at the end, as part of the completion contract in docs/development/README.md. Keep it short: it is a pointer, not a summary of the project. Per-item definitions live in the phase file, history lives in the log, and neither is repeated here. When the owner names new work, this file gains a current item again; until then it stays none.