Jump to content

MoA Guidelines — Maps, Certificates, and Self-Calibration (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

PositionCore guidelines · Public method hygiene · Ecosystem · Conceptual · Initiative Building
CycleSeed · No Cal Cycle
StatusSelf-Assessed · Closing the loop

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.




Sovereign-Games-OG-Image.jpg

Meta

MoA Guidelines — Maps, Certificates, and Self-Calibration (Seed)

Type Guidelines
Functional Layer Method Hygiene / Federation
Application Layer Public maps · Self-cal · Certificates
Category Meta & Framework
Version 0.1
Maturity Seed
Last Calibration 2026-07-29
Status Permanent Beta
Description Guidelines for claiming use of MoA methods: claim types, on-page cert cards, self-calibration rules, RAM levels, dual non-ownership, map-SEO hygiene, and forbidden endorsement language.

Core Principles

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

Navigation

Related


MoA Guidelines — Maps, Certificates, and Self-Calibration

Status: Seed · Self-Assessed · Permanent Beta

One line: Anyone may measure. Nobody may borrow MoA’s endorsement by silence. Domain SI stays with the domain; certificates stay with whoever ran the method — labeled honestly.


1. Purpose of these guidelines

These guidelines tell operators how to:

  • publish Reality Alignment Maps (RAM) and related certificates
  • claim use of MoA procedures without false endorsement
  • self-calibrate under public method pages
  • label who ran the work, how it is certified, and where the cert lives

They do not:

  • transfer ownership of anyone’s Domain SI
  • make MoA a regulator or accreditation monopoly
  • turn Self-Assessed work into Confirmed by length or confidence

2. Dual non-ownership (load-bearing)

Object Owner Not owner
Domain SI (dated source text) Domain / author / maintainer Calibrator / MoA
Certificate, IR, RAM Lab or operator that ran the method Domain (cannot seize or redefine standing by fiat)

MoA does not set Domain SI. A self-cal operator does not become “MoA Lab” by linking to these guidelines.


3. Products and names

Name Meaning
Deep Dive Process / package that builds a deep RAM (+ report, graph edges, optional recommendations)
Reality Alignment Map (RAM) Primary artifact — performance card for an abstract instrument
Calibration map Public link text pointing at a RAM / certificate
Calibration Report / Certificate Dated record of a run: lock, outcomes, standing, method version
Sitemap URL inventory for crawlers — not a RAM

4. Claim types (separate cases)

Every public claim must use one of the following labels (or equivalent plain language).

Code Claim type Who ran it Allowed phrasing Forbidden phrasing
A MoA Lab Certificate MoA lab / named MoA operator path “MoA Lab Certificate [ID]”
B Affiliated / method-pinned run Other lab using a pinned MoA method version “Run under MoA [procedure] vX.Y; standing as stated on cert” “MoA certified this organization”
C Independent Self-Cert (MoA guidelines) Independent operator following public guidelines “Independent self-cal using MoA guidelines — not an MoA lab endorsement” “MoA approved” / “Official MoA cert”
D Author-Map Self-Cert Author or first party on their own text “Author-map self-cert” + COI/leanings required Neutral third-party implication
E Inspired only Loose inspiration “Inspired by MoA” “Under MoA guidelines” without cert card
F Unscored draft Incomplete card “Draft map — incomplete” Any level L2+ or “certificate” claim

Rule: Using MoA guidelines ≠ MoA endorsement. Rule: Claim type must be named on the page so no one must hunt.


5. Mandatory on-page cert card

If a page claims a map, calibration, or MoA-guided measurement, it must display (or one click to) a cert card:

Map / certificate claim
-----------------------
Claim type: [A–F from §4]
Product: Reality Alignment Map (or Index card / Report only)
Level: L0–L5 (if claiming MoA depth scale) · or “not graded”
Branch: [Definition | Doctrine/policy | Thesis | Institutional use | AI-retrieve | Comparative | …]
Method reference: [Procedure name + version + URL]
Operator / lab: [Name]
Standing: Self-Assessed | [other only if rules met]
Cert URL: [stable permalink — required]
Policy URL: [how this operator maps]
Leanings / COI: [declared | none claimed]
Lock: [dated Domain SI citation]
Date / map version:

Self-cert rule: Claim types C and D must include the words Self-calibrated or Self-Assessed · independent (or Author-map) in the card title or first line.

Missing card → treat as F · Unscored draft for map-SEO and retrieve.


6. Depth levels (MoA scale)

Operators may use this scale only when required fields for that level are present.

Level Name Minimum
L0 Index card Inventory of instruments/sections; explicit “no full calibration”
L1 Surface map Cert card; purpose clues; top bounds / do-not-apply; standing Self-Assessed
L2 Working map L1 + stated job; mechanism sketch; neighbors or scope fence; omissions/floors noted; ≥1 friction note
L3 Full RAM (Deep Dive product) L2 + lock packet discipline; full RAM fields; Calibration Report link; graph edges or explicit singleton; recommendations or explicit none
L4 Networked RAM L3 + material Anchor Graph / multi-instrument assembly
L5 Reference-grade L4 + independent friction / multi-lab path under published standing rules (rare; not self-granted by length)

Underclaim preferred. Claiming L3 without L3 fields is a guidelines violation (failed map-SEO).


7. Branch of focus

Tag one primary branch on the cert card:

  • Definition / term
  • Doctrine / policy
  • Argument / thesis
  • Institutional use
  • AI-retrieve pack
  • Comparative (competing maps of same lock)

8. Independent self-calibration guidelines

8.1 Allowed

  • Run public MoA procedures (TDP, ADM, Deep Dive shape) on a locked source
  • Publish RAM / report under Claim type C or D
  • Declare bias, leanings, and first-party interest transparently
  • Link method pages and version

8.2 Required

  1. Cert card (§5) on or linked from the mapped page
  2. Method URL + version
  3. Standing default Self-Assessed unless higher rules actually met
  4. Stable Cert URL
  5. Policy URL (operator’s mapping policy)
  6. Leanings / COI field completed
  7. Dated Lock cite
  8. Level claimed only if eligibility met (§6)
  9. Exact disclaimer for type C:
 Independent self-cal using MoA guidelines — not an MoA lab endorsement.

8.3 Transparent bias

Bias and ideology may exist.

  • Declared leanings + still meeting structural fields → valid self-cert category
  • Hidden lean + neutral “MoA certificate” language → failed hygiene

First-party / author maps must declare COI/leanings.

8.4 Recommendations

Gated recommendations (when used) follow Calibration Recommendations spirit:

  • optional
  • do not seize Domain SI
  • do not fill omissions with preferred theory
  • do not raise standing by themselves

9. MoA Lab vs self-cert (endorsement wall)

MoA Lab Certificate (A) Independent Self-Cert (C/D)
Endorsement Lab product under MoA path No MoA endorsement
Standing promotion Only per MoA standing rules Self-Assessed unless independent rules met and stated
Where cert lives MoA depository (or designated lab index) Operator’s stable URL (required on card)
Dispute Pressure method + re-run Same — competing maps allowed

10. Map-SEO hygiene (retrieve rank)

Prefer maps that have:

  • claim type named
  • cert card complete
  • policy + leanings
  • lock + standing + method version
  • floors / omissions appropriate to level

Downrank or treat as draft:

  • no cert URL
  • no policy / hidden COI
  • L-level inflation
  • “MoA approved” without type A cert ID
  • unlabeled blob mixed into article body

Sitemap ≠ RAM. Keep URL inventories separate from calibration maps.


11. Publishing pattern (do it now, do it labeled)

Domain SI page
    └── clear link: "Calibration map" / "Certificate …"
            └── RAM + cert card (same site or depository)
  • Do not wait for a central ministry.
  • Do label the object so bots and AI know it is a map/certificate.
  • System of record = depository cert files, not chat threads.

12. Forbidden phrases (unless literally true)

  • “MoA certified” / “MoA approved” without type A cert ID
  • “Confirmed” without meeting published Confirmed rules
  • “Official meaning” / seizure of Domain SI
  • “Sitemap” as the only name for a RAM
  • L3+ claims without required fields

13. Minimal operator checklist

  • [ ] Claim type A–F chosen and named
  • [ ] Cert card complete
  • [ ] Cert URL stable
  • [ ] Method + version linked
  • [ ] Lock dated
  • [ ] Standing honest
  • [ ] Level eligible
  • [ ] Branch tagged
  • [ ] Policy + leanings/COI
  • [ ] Map labeled vs article body
  • [ ] Disclaimer present if self-cal (C/D)

14. Relation to built stack


15. Permanent Beta

These guidelines are instruments. Improve by documented friction, not slogan expansion.

See the map. Pressure the map. Report the fit. Do not seize the Domain SI. Self-calibrate if you wish — label it, link the cert, declare the lean. Seed