Skip to content

Subject Log Lifecycle

Roadmap project documentation for the lifecycle family — a formal-model change giving every subject log the same four occurrence shapes, so that liveness, the tombstone, and the rule that nothing follows a retire are written once instead of hand-built by each adopter.

Every log needs to say the same four things about a subject: it began, it changed, it was affirmed unchanged, it ended. Today each log says them in its own words. Six logs carry their own create predicate, four define liveness for themselves, and the arm refusing a write to a subject that is no longer live is repeated fifteen times in demand alone. Each copy is a place the rule can differ from its neighbours without anything noticing.

  • Lifecycle Shapes — the four shapes, what each may carry, and the three laws that come with them.
  • Affirm — the act that claims a value is unchanged, and why that is an act rather than a read.
  • D13 Contract — the per-adopter table the runtime builds against: names, codes, atoms, effects, and the envelope.

The cut is verified and unmerged. Its Tier A gate is green — every root satisfiable, with the predictions registered before the run — and its Tier B soak has not run. Merging onto the integration line is the operator’s own hand.

One question stays open: the spelling of the business affiliate’s retire kind, stated for veto in the contract table.

One is settled. This project’s account of how reference data ends its life contradicted a published domain page, and the operator ruled on 2026-09-09 that the subject-log shape is of record. Lifecycle Shapes states it, and the superseded page now says so on its face.