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 — Developer note · Information architecture Cycle — Seed Status — Conceptual · No cal cycle · Capture-all 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

Developer Note: RAM, Deep Dive, and Wiki Placement

Status: Seed · Conceptual · No calibration cycle required · Permanent Beta

One line: RAM is the published calibration object; Deep Dive is the deep process/packet; abstracts stay clean; Map/DeepDive live as inspectable certificate pages under a fixed URL standard.

1. Why this note exists

Capture architecture decisions so we stop re-deriving them:

What a RAM is vs a Deep Dive
What belongs on the cert card vs in the logic body
How pages present on a wiki without burdening average readers
How search, categories, and meta keep content and certificates unmixed
What is now vs road

Promote later into separate pages (RAM product guide, Deep Dive procedure, wiki IA) if needed. Length is fine here.

2. Core split

	RAM (Reality Alignment Map)	Deep Dive
Kind	Product / page object	Process + work packet
Job	Operable performance card under a lock	Run deep measurement; emit full packet
Public link text	Calibration map	Deep Dive report (when present)
Can exist alone?	Yes (L0–L2 especially)	Incomplete without map/report output
Default depth	L0–L5 scale on card	Targets L3+ body + report/IR

Deep Dive (process)
       ↓
 Report / IR  +  RAM body (L3+)  +  optional graph + gated recs
       ↓
Published Calibration map page = RAM + cert card

Cert card ≠ Deep Dive. Card = pre-filter, claim type, standing, lock, level. Body = logic map of the abstract. Deep Dive = disciplined run that produces a full body + certificate trail.

3. Importance lists

RAM matters because

Retrieve object for humans and AI (structure without re-eating Domain SI)
Map-SEO / pre-filter (slop visible before full-page read)
Level claims (L0–L5) stay honest
Federation (competing maps, self-cal)
Daily use — most needs are map-sized, not research-sized
Dual non-ownership — map does not seize Domain SI

Deep Dive matters because

Depth: mechanism, reality contact, worked chains, floors
Lock discipline and anti-laundering
Packet: report/IR, not only opinion
High-stakes / hostile / thick sources
Optional modules (argument scan, coherence) as capability grows
Lab credibility under pressure

4. Cert card vs RAM body

Layer	Contents
Cert card	Claim type; product; level; branch; method+version; operator; standing; cert URL; policy; leanings/COI; lock cite; date
RAM body	Purpose-as-job; mechanism prose/tables; reality contact; worked chains; bounds; floors; distortions; neighbors; optional modules
Deep Dive extras	Full Stage-0-class lock evidence; report ID; IR; graph edges; friction log; gated recommendations or explicit none

Missing card → unscored draft for retrieve. Card only, almost no body → L0–L1 surface, not “Deep Dive.”

5. Depth levels (reminder)

Level	Name	Body expectation
L0	Index card	Inventory; explicit no full cal
L1	Surface map	Purpose clues + top bounds + card
L2	Working map	Mechanism sketch + friction notes
L3	Full RAM	Deep logic body + report link (Deep Dive product)
L4	Networked RAM	L3 + Anchor Graph / assembly
L5	Reference-grade	Independent friction path under published rules (rare)

6. Optional body modules (including future)

Module	Asks	Default now?
M1 Instrument	Job / mechanism	Yes
M2 Reality contact	Observables / pass-fail	Yes at L2+
M3 Argument scan	What the document asserts sectionally	Optional / road for long prose
M4 Coherence	Contradictions, sense shifts	Optional / road
M5 Support	Definitional vs evidence-needing claims	Optional / road

Paragraph-level “sound/unsound” analysis is in family but not required on every map. Prefer fit / distortion / unsupported / contradiction / out of scope over moral “good/bad paragraph.”

7. Presentation — do not burden the average reader

Abstract page stays a normal page. Depth is linked.

Visible minimum on abstract:

Calibration map: Map:Title (L# · Standing)
Deep Dive: DeepDive:Title_YYYY-MM-DD   ← only if packet exists

No cert card wall in the article lead. No mandatory map before reading.

8. Wiki URL standard (adopted preference)

/wiki/Open_source                         ← abstract / Domain SI content
/wiki/Map:Open_source                     ← RAM (canonical calibration object)
/wiki/DeepDive:Open_source_2026-07-29     ← dated run packet
/wiki/Maps                                ← hub index of maps
/wiki/Deep_Dives                          ← optional hub of packets

Rules:

One canonical RAM per instrument version
Deep Dive pages link to canonical Map; avoid drifted duplicate bodies
Prefer MediaWiki namespaces `Map:` and `DeepDive:` (or site-wide subpage rule `Title/Map`) — pick one and keep it
Normal wiki pages + templates — not a second CMS required at Seed

Template

{{CertCard|…}} required at top of every Map page (and Deep Dive report cover).

9. Search, categories, inspectability

Goal: functional and inspectable; not mixed into casual abstract search.

Namespace	Default search	Browse
Main (abstracts)	On	Normal content
Map:	Off default (or separate profile)	Hub + direct links + cert URLs
DeepDive:	Off default	Hub + links from Map/abstract

Categories:

Map/DeepDive use cert categories (`Reality Alignment Maps`, `Deep Dive reports`)
Do not file Map pages into the same topic category lists as abstracts if that mixes “content” browse
Category bars may be visually hidden on cert pages via skin/CSS; categories remain real for maintenance and inspection
Nothing secret — URL and hub access preserved

10. Meta: certificates, not second abstracts

Map and DeepDive pages are certificate-type objects. They do not replace Domain SI and are not “another abstract to certify.”

Example meta hooks:

moa:object-type = calibration-certificate
moa:domain-si   = https://…/wiki/Open_source
moa:map-level   = L2
moa:standing    = Self-Assessed
moa:claim-type  = C-independent-self-cert

Robots policy is a choice:

`noindex,follow` — certs don’t compete as articles; still followable
`index,follow` — stronger map-SEO discovery

Either way, object-type must mark certificate vs content.

Abstract pages: normal content meta + link to map.

11. Claim types and self-cal (pointer)

Full taxonomy lives in MoA Guidelines (Maps, Certificates, Self-Calibration):

A MoA Lab Certificate
B Method-pinned affiliate run
C Independent Self-Cert (MoA guidelines) — disclaimer required
D Author-map Self-Cert — COI required
E Inspired only
F Unscored draft

Using guidelines ≠ MoA endorsement. Cert URL and claim type must be on the card, not hidden.

12. Map-SEO and triage wall

Map-SEO disciplines default discoverability / retrieve priority, not speech and not Domain SI.

Crooked maps may exist; they need not win rank
Silence can mean capacity limits, not only guilt
Missing/theatrical card → downrank or skip before full-page read
That is instrument triage, not censorship
Benefit to crawlers/packs: less junk-drawer load

Related declaration: optimize for best calibration object, not only clicks — with this wall intact.

13. Auto-cal later (non-cert)

Road-friendly:

Machine draft L0–L1 sketches from crawl
Must label Draft · machine-assisted · not a certificate
No Claim type A; no inflated standing
Human/lab edit promotes to real RAM levels

14. What we are doing vs what we can do

Activity	Now	Road
RAM L0–L2 + cert cards	Yes	Scale
Deep Dive L3 packets	Selective	More instruments
Wiki IA (Map: / DeepDive:)	Adopt	Enforce in skin/search
Argument/prose modules M3–M5	Optional experiments	Standard product
Auto draft maps	Concept	Pipeline
Full-book paragraph audit default	No	Possible under argument branch

15. Operator checklist (wiki publish)

[ ] Abstract page clean — one Calibration map link (+ Deep Dive link if any)
[ ] `Map:Title` canonical RAM with `Template:CertCard`
[ ] Level/branch/standing honest
[ ] Body matches level (no L3 claim on L1 sketch)
[ ] DeepDive dated page links to canonical Map
[ ] Namespaces not in default abstract search mix
[ ] Meta object-type = certificate on Map/DeepDive
[ ] Hub listing on `Maps`
[ ] Dual non-ownership footer

16. One-line doctrine

Abstracts are content; Maps are calibration objects; Deep Dives are deep run packets; keep them linked, labeled, unmixed in search, light on the reader, heavy on inspectable structure.

See also: MoA Guidelines — Maps, Certificates, and Self-Calibration · Deep Dive — Reality Alignment Mapping · Domain SI · Map-SEO notes · Declaration: Optimize the Page as a Calibration Object

Type	Development Note
Functional Layer	Process Reference / Site IA
Application Layer	Wiki · RAM · Deep Dive · Discovery
Category	Development Notes
Version	0.1
Maturity	Seed
Last Calibration	2026-07-29
Status	Permanent Beta
Description	Capture-all note: RAM vs Deep Dive, levels, body vs cert card, wiki URL standard, search/category separation, meta as certificates, presentation burden, auto-draft future, argument modules road.

Developer Note: RAM, Deep Dive, and Wiki Placement (Seed)

Meta

Menu