Jump to content

Developer Note: Three Surfaces (MoA Root · Cal Lab · TSG) (Seed)

From The Sovereign Games (MoA Lab)

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

PositionDeveloper note · Lab surfaces
CycleSeed
StatusConceptual · 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.


Developer Note: Three Surfaces (MoA Root · Cal Lab · TSG)

One line: MoA publishes the rules and the clean cal objects; the lab runs certificate paths; TSG keeps the bench dirty enough to invent and hard enough to prove.



Sovereign-Games-OG-Image.jpg

Meta

Developer Note: Three Surfaces (MoA Root · Cal Lab · TSG) (Seed)

Type Development Note
Functional Layer Process Reference / Site IA
Application Layer MoA · Cal lab · TSG
Category Development Notes
Version 0.1
Maturity Seed
Last Calibration 2026-07-29
Status Permanent Beta
Description Three surfaces: MoA root (standards and rules), MoA cal lab (clean certificates), TSG (shop-floor production and tracking). Roles, promote path, claim hygiene, hostname direction.

Core Principles

  • Reality gets final vote
  • See the Game. Refuse the Game. Build Better.
  • Permanent Beta

Navigation

Related



1. Why three surfaces

One production wiki cannot be both shop floor and certificate wall without confusing adopters.

  • People looking for standards, procedures, rules, and lists need a light, stable front.
  • People needing something calibrated need a clean cert surface — not redlink culture and draft sprawl.
  • People building and stress-testing conceptual instruments need a messy, honest bench.

Same duty. Different surfaces.


2. Role table

Surface Job Feel Typical contents
MoA root Standards desk Professional, light, stable What MoA is; standards & procedures index; claim types; dual non-ownership; governance note (lab path only); Future Lab On-Ramp; links out
MoA cal lab Certificate wall Clean lab; cite-ready RAM / maps; cert cards; reports; standing labels; stable cert URLs; promote-only drafts barred from default browse
TSG Shop floor Happy mess; production OK Diagnostic games; builder tools; R&D; calibration logs; Admin status; Calibration Debt; sandbox stress-tests under incentives and drift

Hostname direction (preference, not locked DNS):

metrologyoftheabstract.org           → MoA root
cal.metrologyoftheabstract.org       → cal lab (or /cal · maps. · certs.)
tsg.metrologyoftheabstract.org       → TSG shop (or current TSG wiki host)

Exact hosts may change. Roles should not blur.


3. Who comes for what

Need Surface
Standards, cals-as-rules, procedures, regs for how we label certs MoA root
“Calibrate this” / published map / report / standing on a cert path MoA cal lab
Develop games, logs, experiments, tracking, visible debt TSG

Independent operators may adopt public procedures without joining MoA governance. Adoption is optional. Using guidelines ≠ MoA endorsement unless claim type and cert say so.


4. TSG and MoA relationship

  • TSG is the primary sandbox domain of MoA — human-systems instruments, diagnostics, builder practices, governance kit under load.
  • TSG does not own MoA. MoA remains portable across domains.
  • TSG does the heavy lifting and tracking for much instrument work; trails and logs live on the shop floor.
  • MoA root and cal lab stay standardized; deep packets and develop history link back to TSG (or lab archives) when inspectability requires it.

Domain SI for TSG content stays with that domain. MoA does not seize it by hosting a link or a cert index.


5. Promote path (shop → wall)

TSG (develop, debt OK, Permanent Beta in public)
        ↓  fit check: purpose, lock, level honest, card complete
MoA cal lab (cite-ready map / report)
        ↓  if it is a standard or procedure
MoA root list (indexed, stable pointer)
  • Drafts and half-built instruments stay on TSG.
  • Cal lab default browse is promoted objects only.
  • Root lists procedures and standards, not every experimental page.
  • “Pass, no edit” on a cycle remains a good outcome after promotion.

6. What each produces (short)

MoA root Standards and procedures index · claim hygiene · on-ramp · portable duty statement · governance scope limited to MoA cert paths.

MoA cal lab Published calibration objects (RAM, reports) · cert cards · standing as labeled · stable URLs for retrieve and map-SEO.

TSG Diagnostic games · builder tools · sandbox stress-tests · anti-capture kit · strategy/memory patterns · lab infrastructure (templates, logs, status fields) · visible Calibration Debt.


7. Clean vs mess (doctrine)

Shop (TSG) Wall (cal lab) / desk (root)
Red links as debt markers OK Debt not the default public face
Seed and experiment expected Level and standing must match body
Tracking, jobs, admin fields Cite card + body; trail via link
Happy mess provider Prestigious only as checkable, not theatrical

Sometimes you must be messy at shop level. The certificate wall does not host that mess.

Lab culture (shop → wall)

  • No memory hole — Valid ideas are treated with respect and drafted (Seed note, stub, or Calibration Debt link). They are not discarded because they arrived in conversation or look early.
  • No cal cycle dread — Ideas are seeded where they belong until moved into production develop and, when fit, certification. A calibration cycle confirms fitness; it is not a punishment for seeding. “Pass, no edit needed” is a good outcome.
  • No premature wall — Half-built objects stay on TSG. Cite-ready standing waits on promote + honest level/claim type.

8. Governance boundary (repeat)

Any MoA lab governance, standing rules, or internal regulatory structure applies to certificates on an MoA lab path (e.g. claim type A and designated indexes).

Independent self-cal (e.g. claim type C) may use public guidelines on other hosts. Optional. Not endorsement by default.


9. Deferred

  • Full MoA-side automation of cycles and dashboards
  • Final choice of cal lab stack (minimal wiki vs HTML+repo vs other)
  • Exact subdomain DNS cutover schedule

Now: hold the role split; seed without dread on TSG; promote to cal/root when fit; keep root list readable; do not memory-hole workable ideas.


10. One-line doctrine

MoA root lists the rules; MoA cal lab hangs the clean certificates; TSG is the happy mess that invents, tracks, and proves — seed with respect, promote up, link back, leave Domain SI alone.


See also: Developer Note: Domains, Not Initiatives · Developer Note: RAM, Deep Dive, and Wiki Placement · MoA Guidelines — Maps, Certificates, and Self-Calibration · Future Lab On-Ramp · Permanent Beta · Seed to Fruit Development · Calibration Debt