Promotion & Traceability Regime (Seed): Difference between revisions
Seed planted |
mNo edit summary |
||
| Line 4: | Line 4: | ||
|status = Self-Assessed · Permanent Beta | |status = Self-Assessed · Permanent Beta | ||
}} | }} | ||
= Promotion & Traceability Regime = | |||
'''Status:''' Seed · Self-Assessed · Permanent Beta | |||
'''One line:''' | |||
'''Bench creates. Lab certifies. Top exhibits. Change always returns to Bench.''' | |||
Traceability is required '''now''' — not only as a future ideal. This regime ''is'' how the lab establishes it. | |||
{{GameModule | {{GameModule | ||
| type = Core Principle | | type = Core Principle | ||
| Line 15: | Line 23: | ||
}} | }} | ||
= | == 1. Authority under our own rules (and what that does not mean) == | ||
National institutes (e.g. NIST) do '''not''' negate this lab’s authority to define '''how certificates and claim types work under MoA procedures'''. | National institutes (e.g. NIST) do '''not''' negate this lab’s authority to define '''how certificates and claim types work under MoA procedures'''. | ||
| Line 49: | Line 49: | ||
NIST-class posture is '''cousin''', not master of our certificate rules. Dual non-ownership remains: Domain SI stays with the domain; '''certs stay with the chain that issued them'''. | NIST-class posture is '''cousin''', not master of our certificate rules. Dual non-ownership remains: Domain SI stays with the domain; '''certs stay with the chain that issued them'''. | ||
== 2. Why traceability now == | |||
Traceability is not a later prestige feature. Without it: | Traceability is not a later prestige feature. Without it: | ||
| Line 60: | Line 60: | ||
'''This regime establishes traceability for present use''' — operators, AI retrieve, competing labs, and future history. The future of the lab ''is'' this chain running today under Seed standing until friction improves it. | '''This regime establishes traceability for present use''' — operators, AI retrieve, competing labs, and future history. The future of the lab ''is'' this chain running today under Seed standing until friction improves it. | ||
== 3. Three layers == | |||
{| class="wikitable" | {| class="wikitable" | ||
| Line 86: | Line 86: | ||
Aligns with three surfaces (root / cal lab / shop) without requiring a specific vendor stack. Roles matter more than software brands. | Aligns with three surfaces (root / cal lab / shop) without requiring a specific vendor stack. Roles matter more than software brands. | ||
== 4. Workflow == | |||
BENCH | BENCH | ||
| Line 111: | Line 111: | ||
Never edit Top as if it were Bench | Never edit Top as if it were Bench | ||
== 5. Mandatory metadata (every certified / Top artifact) == | |||
'''Regime identity''' — under which certification structure | '''Regime identity''' — under which certification structure | ||
| Line 123: | Line 123: | ||
No public trust artifact points at uncertified draft state as if it were the freeze. | No public trust artifact points at uncertified draft state as if it were the freeze. | ||
== 6. What each layer must not do == | |||
{| class="wikitable" | {| class="wikitable" | ||
| Line 139: | Line 139: | ||
|} | |} | ||
== 7. Dictionary — trust surface, not workbench == | |||
'''Prior mental model:''' Dictionary as Bench module → '''wrong.''' | '''Prior mental model:''' Dictionary as Bench module → '''wrong.''' | ||
| Line 168: | Line 168: | ||
'''Rule:''' Canonical dictionary URL never resolves to “edit this page / unresolved breadcrumb farm” as the authority object. It resolves to '''certified text + cert trail'''. | '''Rule:''' Canonical dictionary URL never resolves to “edit this page / unresolved breadcrumb farm” as the authority object. It resolves to '''certified text + cert trail'''. | ||
== 8. Outside labs (welcome, not chaos) == | |||
Open to external calibration labs '''under this regime''' (shared or adopted procedures, standing rules, evidence bar). | Open to external calibration labs '''under this regime''' (shared or adopted procedures, standing rules, evidence bar). | ||
| Line 176: | Line 176: | ||
Prevents both closed priesthood and “anyone pastes into the dictionary.” | Prevents both closed priesthood and “anyone pastes into the dictionary.” | ||
== 9. Relationship to other doctrine == | |||
[[Domain SI — We Calibrate, We Do Not Set]] — regime authority ≠ Domain SI ownership | [[Domain SI — We Calibrate, We Do Not Set]] — regime authority ≠ Domain SI ownership | ||
| Line 185: | Line 185: | ||
Claim types & map guidelines — self-cal ≠ Lab cert | Claim types & map guidelines — self-cal ≠ Lab cert | ||
== 10. Stack note (non-normative) == | |||
Roles are normative. Software is not: | Roles are normative. Software is not: | ||
| Line 195: | Line 195: | ||
Implement with tools that preserve the chain. Do not delay the regime for architecture theater. | Implement with tools that preserve the chain. Do not delay the regime for architecture theater. | ||
== 11. One-line regime == | |||
'''Authority to label certificates under this regime runs on a defined chain: Bench produces candidates; Lab grants standing under published procedures; Top only shows what Lab has frozen; dictionary is a certified reference product; traceability starts now; we answer to scrutiny, transparency, and metrology — not to permission from another institute.''' | '''Authority to label certificates under this regime runs on a defined chain: Bench produces candidates; Lab grants standing under published procedures; Top only shows what Lab has frozen; dictionary is a certified reference product; traceability starts now; we answer to scrutiny, transparency, and metrology — not to permission from another institute.''' | ||
Revision as of 09:04, 30 July 2026
Welcome to the MoA–TSG Lab. The wiki is the bench. The work is Metrology of the Abstract. Adopt the tools or leave them on the rack — either way, the need doesn't wait.
- Lab Note: A redlink is not a failure. It identifies Calibration Debt—work waiting to be measured, mapped, and calibrated.
|
CYCLE Calibration position Position — Core regime · Traceability Cycle — Seed Status — Self-Assessed · Permanent Beta
This page is a conceptual instrument under Permanent Beta. It declares a real calibration position, not a finished product waiting to ship. Checking continues; an edit is only required when evidence demands it. Stage: Seed to Fruit. Feedback welcome — especially clarity, failure modes, and calibration gaps. Use discussion or Contribute. |
Promotion & Traceability Regime
Status: Seed · Self-Assessed · Permanent Beta
One line: Bench creates. Lab certifies. Top exhibits. Change always returns to Bench. Traceability is required now — not only as a future ideal. This regime is how the lab establishes it.
Meta
Promotion & Traceability Regime (Seed)
| Type | Core Principle |
|---|---|
| Functional Layer | Lab governance / Traceability |
| Application Layer | Bench · Lab · Top · Dictionary · External labs |
| Category | Meta & Framework |
| Version | 0.1 |
| Maturity | Foundational (Seed standing) |
| Last Calibration | 2026-07-30 |
| Status | Permanent Beta |
| Description | Promotion and traceability regime: Bench creates, Lab certifies, Top exhibits; change returns to Bench. Own certificate authority under published rules; scrutiny and metrology as the answerability standard. Dictionary as trust surface. Traceability required now. |
Menu
Core Principles
- Reality gets final vote
- See the Game. Refuse the Game. Build Better.
- Permanent Beta
Navigation
Related
1. Authority under our own rules (and what that does not mean)
National institutes (e.g. NIST) do not negate this lab’s authority to define how certificates and claim types work under MoA procedures.
| We claim | We do not claim |
|---|---|
| Authority to set regime rules for promotion, freeze, standing labels, and how others may claim “certified under this regime” | Ownership of any domain’s Domain SI (statutes, plant SOPs, OSI text, etc.) |
| Answerability to scrutiny, transparency, and metrology practice | Freedom from challenge, friction, or independent re-runs |
| Right to refuse Bench “we’re done” when procedure is not met | Monopoly on all abstract calibration worldwide |
| Portable procedures others may adopt or fork under their standing | That adoption = our endorsement unless claim type says so |
We answer to no ministry for permission to run this chain. We answer to scrutiny, transparency, and metrology itself — the same family of pressure serious measurement culture already accepts.
NIST-class posture is cousin, not master of our certificate rules. Dual non-ownership remains: Domain SI stays with the domain; certs stay with the chain that issued them.
2. Why traceability now
Traceability is not a later prestige feature. Without it:
Public artifacts point at moving Bench pages “Certified” becomes a vibe Re-cal and audit cannot find the freeze External labs cannot plug in without chaos
This regime establishes traceability for present use — operators, AI retrieve, competing labs, and future history. The future of the lab is this chain running today under Seed standing until friction improves it.
3. Three layers
| Layer | Name | Function | Public trust role |
|---|---|---|---|
| Bench | Workbench / sandbox (e.g. TSG shop) | Draft, argue, test, Permanent Beta, structural mess, Calibration Debt | None as certificate — may be public as bench, never as cert authority |
| Lab | Calibration lab | Review, improve or refuse, issue freeze/cert under published procedures | Certificate authority for artifacts it accepts under this regime |
| Top | Authority / standards face | Host certified freezes, maps, deep-dives; prefer fast static or static-generated | Exhibition only — never performs calibration |
Aligns with three surfaces (root / cal lab / shop) without requiring a specific vendor stack. Roles matter more than software brands.
4. Workflow
BENCH
Develop until promotion is requested (candidate complete enough to ask Lab — not “public ready by vibes”) Good enough, better than hit or miss — honest level and standing
LAB
Review against published procedures + this regime · Accept → improve if needed → certify / freeze record · Refuse → return to Bench with reasons Lab does not owe acceptance of Bench’s “we’re done.”
TOP
Publish only Lab-certified artifacts No live calibration on Top No silent mutation of certified text
CHANGE / RE-CAL
Signal (field use, cycle, error, regime rule, regime shift) → Bench rework → Lab re-cert → Top replaces prior freeze (prior freeze remains in history) Never edit Top as if it were Bench
5. Mandatory metadata (every certified / Top artifact)
Regime identity — under which certification structure Lab identity — who certified (this lab or external lab under regime rules) Procedure / standard IDs + versions used Artifact version + freeze date Standing / result summary as lab procedures define Pointer to Lab record — not to Bench talk, open breadcrumb farms, or Active Development as the cert target Claim type (e.g. MoA Lab path vs independent self-cal under guidelines) when applicable
No public trust artifact points at uncertified draft state as if it were the freeze.
6. What each layer must not do
| Layer | Forbidden |
|---|---|
| Bench | Issue public certs under this regime; act as Top; present draft as freeze |
| Lab | Point certs at uncertified Bench pages as the authority URL; skip published procedure; seize Domain SI |
| Top | Perform calibration; silently revise certified text; host drafts as authority face |
7. Dictionary — trust surface, not workbench
Prior mental model: Dictionary as Bench module → wrong.
Dictionary is a trust surface: definitions people will treat as reference. That is Lab + Top territory for canonical URLs.
| Aspect | Where |
|---|---|
| Drafting terms, disputes, alternatives | Bench (staging / working area) |
| Accepted definition, version, cert status | Lab (review + certify) |
| Public lookup, clean UX, stable URLs | Top (or Top-facing hybrid) fed only by certified entries |
Hybrid Dictionary model:
Public face: clean lookup, stable URLs, reads like a reference instrument — not an edit war. Lab cert: each published entry carries regime metadata (who certified, version, date, procedure). Outside labs: may submit or co-certify only through Lab gates under this regime — not by editing the public face directly. Bench: proposals and dispute history linked as development trail — not the canonical definition URL.
Rule: Canonical dictionary URL never resolves to “edit this page / unresolved breadcrumb farm” as the authority object. It resolves to certified text + cert trail.
8. Outside labs (welcome, not chaos)
Open to external calibration labs under this regime (shared or adopted procedures, standing rules, evidence bar). They do not become a second Top. They issue or co-sign through Lab process; Top only exhibits what the regime has certified. Independent operators may still run self-cal under public guidelines (claim type distinct) without becoming regime Lab — honesty of claim type required. Prevents both closed priesthood and “anyone pastes into the dictionary.”
9. Relationship to other doctrine
Domain SI — We Calibrate, We Do Not Set — regime authority ≠ Domain SI ownership Doctrine: Good Enough, Better Than Hit or Miss — Lab may certify lower levels when the abstract caps depth; underclaim required Seed to Fruit Development — Bench seeds; Lab/Top fruit for trust URLs Developer Note: Domains, Not Initiatives — need-based promotion, not campaign theater Developer Note: Three Surfaces — root / cal / shop roles Claim types & map guidelines — self-cal ≠ Lab cert
10. Stack note (non-normative)
Roles are normative. Software is not:
Top often fits static or static-generated HTML for speed and a calm face Lab needs stable cert records (wiki namespace, repo, or later systems) — not necessarily a client portal on day one Bench fits wiki / workbench collaboration
Implement with tools that preserve the chain. Do not delay the regime for architecture theater.
11. One-line regime
Authority to label certificates under this regime runs on a defined chain: Bench produces candidates; Lab grants standing under published procedures; Top only shows what Lab has frozen; dictionary is a certified reference product; traceability starts now; we answer to scrutiny, transparency, and metrology — not to permission from another institute.
See the map. Pressure the map. Report the fit. Do not seize the Domain SI. Bench creates. Lab certifies. Top exhibits. Change returns to Bench.