`ADHOC-YYYY-MM-DD` is unique per date but not per repository, so any two repos
opening an ad-hoc on the same day collide. The 2026-08-26 fleet projection
reset refused 9 records for exactly this reason.
Canon (work-record-types_v0.1, CUST-WP-0066) settled the form as
`{PREFIX}-WP-ADHOC-YYYY-MM-DD`, filename unchanged, and grandfathered existing
ids on the condition they are never *silently* re-derived. This is the explicit
migration that clause allows for.
The hub id is derived from the record id, so a changed id is a different
record: stale state_hub_*_id fields are dropped and fix-consistency re-derives.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
These workplans exist only in the retired local hub. Their random pre-ADR-007
identifiers are refused by C-06 as stale references, so they cannot be
registered. Deriving from the canonical record id takes no identity from
anything: central does not hold them and the old ids die with the cache.
Records central already holds were deliberately left untouched.
Refs CUST-WP-0068-T06
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
Offered by tenant-engine alongside TEN-WP-0010. Their resolver already has a
precedence layer where a plan-derived limit outranks a grouping default, and
it has no feed. Ceilings currently swing EUR 250 to EUR 20,000 on a headcount
proxy that nobody approved commercially.
Proposed rather than ready: the interface shape is not yet agreed with
tenant-engine, so T01 settles it and T02-T04 wait on that.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
T02-T04 were completed 2026-08-18; the draft-8 outcome section still said
they were outstanding. Replies sent to railiance-platform (section 11
correction accepted; tier-P-floor trigger accepted as ours, narrowing our
earlier blanket monitoring caveat) and tenant-engine (grouping unaffected,
Q5 ownership agreed, plan-derived ceiling interface welcomed as new scope).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Decision 5.3 makes n/a an admissible level, which is what T01 needed; withdraw
finding 6 and adopt tenancy.yaml rather than proposing a format. Findings
1-5 and 7 survive because section 11 is byte-identical across drafts 5-7 —
four repos reviewed and none touched the commercial section, which is ours.
Records the sellability read: with flex-auth at A0, apps-pg at R0 and
tenant-engine on SQLite, no tier can support an isolation, availability or
retention claim today. Notes that section 5.5 provider declarations mean
T02 must reference two levels, not one.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Bernd's call: option C without the scoped-veto bridge. A veto would only
protect existing claim-bearing tiers and there are none, so not being live
is what makes the direct move safe. Records a named revisit trigger.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Draft-6 (net-kingdom 2744ce7) applies tenant-engine's review only; findings
1-5 all still stand. Adds two findings from draft-6 itself: off-ladder
notation (P-, R0/R1) with no declaration form, and no obligation to notify
dependent tiers when a delivering service downgrades its posture. Reframes
T06 to reuse draft-6's level-plus-named-exception grammar.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Responds to rapp-postgres review request on NetKingdom Tenancy Posture v0.1.
Covers posture-vector publication, an assurance-claims extension to the
canonical pricing schema, boundary validation, a tier-definition gate, and
the Q5/Q2 answers. Records five findings against the framework for
amendment while it is still proposed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add file-based Bubble, Stripe, and OpenRouter importers; usage attribution,
cost allocation, pricing simulator, credit wallets, and recommendations in the
dashboard API. Document whynot-design UI workflow and archive the finished
workplan with all ten tasks marked done.
Set bootstrap workplan active and finish all tasks: refine SCOPE.md and
README.md, add Dev Workflow and credential routing to AGENTS.md, propagate
.claude/rules/credential-routing.md, and document early-phase verification
commands (fix-consistency, registry sanity check).
Convert legacy AdaptivePricing-MVP-Workplan.md into
ADAPTIVE-WP-0002-economic-observatory-mvp.md with ADR-001 frontmatter,
eight sprint task blocks, and State Hub workstream registration. Mark
bootstrap task T03 done after seeding the first implementation workplan.
