The Sovereign Games (MoA Lab) - Recent changes [en]

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

Sovereign — Thu, 30 Jul 2026 01:14:06 GMT

10. One-line doctrine

← Older revision		Revision as of 21:14, 29 July 2026
(2 intermediate revisions by the same user not shown)
Line 144:		Line 144:
	Sometimes you '''must''' be messy at shop level.		Sometimes you '''must''' be messy at shop level.
	The certificate wall does not host that mess.		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) ==		== 8. Governance boundary (repeat) ==

Line 159:		Line 165:
	* Exact subdomain DNS cutover schedule		* Exact subdomain DNS cutover schedule

	'''Now:''' hold the role split; ~~develop~~ on TSG; promote to cal/root when fit; keep root list readable.		'''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 ==		== 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 — promote up, link back, leave Domain SI alone.'''		'''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.'''

	----		----

Main Page

Sovereign — Thu, 30 Jul 2026 01:07:45 GMT

← Older revision		Revision as of 21:07, 29 July 2026
Line 4:		Line 4:
	'''Welcome to the MoA–TSG Lab.''' The wiki is the '''bench'''. The work is '''Metrology of the Abstract'''.		'''Welcome to the MoA–TSG Lab.''' The wiki is the '''bench'''. The work is '''Metrology of the Abstract'''.
	<b><i>Adopt the tools or leave them on the rack — either way, the need doesn't wait.</i></b>		<b><i>Adopt the tools or leave them on the rack — either way, the need doesn't wait.</i></b>

			== 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 — promote up, link back, leave Domain SI alone.'''

	*<small>'''Lab note:''' A red link is not a failure. It marks [[Calibration Debt]] — work waiting to be measured, mapped, and calibrated.</small>		*<small>'''Lab note:''' A red link is not a failure. It marks [[Calibration Debt]] — work waiting to be measured, mapped, and calibrated.</small>

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

Sovereign — Thu, 30 Jul 2026 01:06:45 GMT

Sovereign moved page Developer Note: Three Surfaces (MoA Root · Cal Lab · TSG) to Developer Note: Three Surfaces (MoA Root · Cal Lab · TSG) (Seed) Seed planted

← Older revision		Revision as of 21:06, 29 July 2026
(2 intermediate revisions by the same user not shown)
Line 6:		Line 6:

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

	~~'''Status:''' Seed · Conceptual · Self-Assessed · Permanent Beta~~

	'''One line:'''		'''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.		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.
Line 21:		Line 18:
	\| 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.		\| 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.
	}}		}}


	----		----
	== 1. Why three surfaces ==		== 1. Why three surfaces ==

	One production wiki cannot be both shop floor and certificate wall without confusing adopters.		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 looking for '''standards, procedures, rules, and lists''' need a light, stable front.
Line 67:		Line 63:
	</pre>		</pre>

	Exact hosts may change. Roles should not blur.		Exact hosts may change. '''Roles''' should not blur.

	----		----

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

Sovereign — Thu, 30 Jul 2026 01:00:46 GMT

seed planted

New page

{{Development Notice
|position = Developer note · Lab surfaces
|cycle = Seed
|status = Conceptual · Self-Assessed · Permanent Beta
}}

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

'''Status:''' Seed · Conceptual · Self-Assessed · Permanent Beta

'''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.
{{GameModule
| type = Development Note
| category = [[:Category:Development Notes|Development Notes]]
| Calibration Type = Process Reference / Site IA
| Application Layer = MoA · Cal lab · TSG
| Version = 0.1
| Maturity = Seed
| Last Updated = 2026-07-29
| 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.
}}

----
== 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 ==

{| class="wikitable"
! 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):'''

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

Exact hosts may change. **Roles** should not blur.

----
== 3. Who comes for what ==

{| class="wikitable"
! 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) ==

<pre>
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)
</pre>

* 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) ==

{| class="wikitable"
! 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.

----
== 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; develop on TSG; promote to cal/root when fit; keep root list readable.

----
== 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 — 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]]

[[Category:Development Notes]]
[[Category:Seed]]
[[Category:Meta & Framework]]

Main Page

Sovereign — Thu, 30 Jul 2026 00:32:51 GMT

Lab rack (navigate by need)

Show changes

Developer Note: Domains, Not Initiatives (Seed)

Sovereign — Wed, 29 Jul 2026 23:33:20 GMT

← Older revision		Revision as of 19:33, 29 July 2026
Line 16:		Line 16:

	= Developer Note: Domains, Not Initiatives =		= Developer Note: Domains, Not Initiatives =

	~~'''Status:''' Seed · Self-Assessed · Permanent Beta~~

	'''One line:'''		'''One line:'''
	MoA does not collect initiatives. It writes calibration procedures for domains, builds a metrology system ''inside'' those domains using their own surfaces, and supports re-runnable certificates — Domain SI stays with the domain.		MoA does not collect initiatives. It writes calibration procedures for domains, builds a metrology system ''inside'' those domains using their own surfaces, and supports re-runnable certificates — Domain SI stays with the domain.

Developer Note: Domains, Not Initiatives

Sovereign — Wed, 29 Jul 2026 23:32:41 GMT

Sovereign moved page Developer Note: Domains, Not Initiatives to Developer Note: Domains, Not Initiatives (Seed) Seed planted

New page

{{Development Notice
|position = Core orientation · Lab duty
|cycle = Seed
|status = Self-Assessed · Permanent Beta
}}
{{GameModule
| type = Development Note
| category = [[:Category:Development Notes|Development Notes]]
| Calibration Type = Orientation / Scope
| Application Layer = MoA lab · Domain work
| Version = 0.2
| Maturity = Seed
| Last Updated = 2026-07-29
| description = Replaces initiative language with domain duty: MoA writes calibration procedures for domains, instruments domain surfaces, provides standards and supporting calibrations without seizing Domain SI. Active domains, future candidates, entry flow, language rules, and non-claims.
}}

= Developer Note: Domains, Not Initiatives =

'''Status:''' Seed · Self-Assessed · Permanent Beta

'''One line:'''
MoA does not collect initiatives. It writes calibration procedures for domains, builds a metrology system ''inside'' those domains using their own surfaces, and supports re-runnable certificates — Domain SI stays with the domain.

----
== 1. Focus shift ==

{| class="wikitable"
! Drop
! Prefer
|-
| “Our initiatives”
| '''Domains we instrument'''
|-
| Campaign / movement branding
| '''Procedures + certificate objects'''
|-
| Portfolio of launches
| '''Need-based depth where measurement gaps cost'''
|-
| MoA as owner of meaning
| '''Dual non-ownership''' (Domain SI theirs; certs with whoever ran the method)
|}

'''Duty statement:'''
As Metrology of the Abstract, the job is to:

* identify abstract instruments that need operable calibration
* write '''procedures''' (Stage 0 / ADM / Deep Dive / claim hygiene / map publish rules)
* use the domain’s own tools where useful (wikis, SEO, repos, catalogs, AI packs)
* provide '''standards and supporting calibrations''' others can re-run
* refuse Domain SI seizure and false endorsement

This is ordinary metrology discipline applied to abstract claims — not a set of branded crusades.

----
== 2. What a “domain” means here ==

A '''domain''' is a field of practice or discourse that already has:

* sources (texts, definitions, policies, code, doctrines)
* users and failure modes
* surfaces (sites, search, repositories, institutions, models)

MoA work in a domain = '''metrology system within it''':

* lock rules
* map / RAM objects
* claim types and standing honesty
* optional Deep Dive packets
* retrieve hygiene (map-SEO) where discovery matters

The domain does not become “an MoA initiative.”
MoA becomes '''usable inside the domain'''.

----
== 3. What MoA provides (same in every domain) ==

{| class="wikitable"
! Deliverable
! Role
|-
| '''Procedures & standards'''
| How to lock, map, grade depth, claim type, publish
|-
| '''Supporting calibrations'''
| Example runs, CR pattern, lab certs when type A applies
|-
| '''Certificate object shapes'''
| RAM, cert card, Deep Dive report, hubs (`Maps`)
|-
| '''Hygiene rules'''
| Endorsement wall, self-cal disclaimer, map-SEO triage wall
|-
| '''On-ramp'''
| Independent labs and operators can re-run without permission theater
|}

MoA does not have to operate every surface.
It must leave '''re-runnable method + honest standing language''' wherever it works.

----
== 4. Active domains (procedure work already in motion) ==

{| class="wikitable"
! Domain
! What MoA is writing / supporting
|-
| '''Public abstracts / wiki & web pages'''
| RAM product shape; Deep Dive process; `Map:` / `DeepDive:` IA; cert cards; dual non-ownership; abstract page stays light
|-
| '''Discovery & retrieve (map-SEO)'''
| Transparency rank signals; pre-filter before full-page read; packs prefer inspectable objects; triage ≠ speech control
|-
| '''Self-cal & federation'''
| Claim types A–F; independent self-cert rules; endorsement wall; operator checklists
|-
| '''Definition / dictionary stack'''
| Stage 0 lock; ADM; term decomposition (TDP); CR pattern (e.g. Fairness floor); dictionary as cal surface under the lab roof
|-
| '''Sovereign Games / diagnostic games'''
| '''Independent lab / human-systems sandbox''' — not an MoA product line; shares method spine; own runs and certificates when issued; game modules as conceptual instruments; Permanent Beta discipline
|-
| '''AI as instrument (not Domain SI)'''
| Retrieve cards; store–map–retrieve; defer-out-of-range; correlated-model honesty; no Confirmed-from-AI-alone
|}

These are '''application domains of the same duty''', not separate movements.

----
== 5. Future domains (procedure candidates) ==

Priority is '''need-based''' — open or deepen a domain when lack of calibration repeatedly costs clarity, standing honesty, or retrieve quality.
Seed list only; order changes under friction — not roadmap theater.

=== 5.1 Near-fit extensions ===

{| class="wikitable"
! Domain
! Likely procedure targets
|-
| '''Policy & doctrine texts'''
| Lock + RAM for operative terms; competing maps; no seizure of legislative Domain SI
|-
| '''License & “open” vocabulary'''
| OSD-class instruments; source-available neighbors; marketing distortion catalog
|-
| '''Standards & specifications clauses'''
| Third-party maps of definition clauses; scope / field-of-use floors
|-
| '''Corporate / product ethics pages'''
| Self-cal rules; COI mandatory; L-level inflation fails rank
|}

=== 5.2 Heavier or later ===

{| class="wikitable"
! Domain
! Likely procedure targets
|-
| '''Academic / theory terms'''
| CR floors; ADM for paper-local use
|-
| '''Institutional mission language'''
| Mission-alignment maps; drift bounds
|-
| '''Education & curriculum claims'''
| Outcome vs intention maps; long-horizon feedback floors
|-
| '''Media / narrative frames'''
| Frame instruments; declare lean on author-maps
|-
| '''Argument modules (long prose)'''
| Optional M3–M5: sectional claims, coherence, support type — fit/distortion language
|-
| '''Auto-draft pipelines'''
| Machine L0–L1 sketches labeled draft-only; human promote to cert levels
|-
| '''Multi-lab standing paths'''
| When independent friction may raise standing without ministry cosplay
|-
| '''Catalogs of mechanism + outcome memory'''
| Memory objects for what was tried and what followed — not ideology scorecards
|}

'''Not on the list as “MoA owns”:** any domain’s primary texts, rankings of moral worth, or speech licensing.

----
== 6. How work enters a domain ==

<pre>
Need (error, ambiguity, retrieve failure, standing theater)
↓
Lock Domain SI (Stage 0 class)
↓
Procedure (ADM / map rules / Deep Dive / claim type)
↓
Certificate object (RAM ± report) on domain surfaces
↓
Re-run / compete / downrank theater
</pre>

Ship '''labeled''' objects early.
Depth scales with need (L0–L2 common; L3+ selective).

----
== 7. Surfaces vs ownership ==

{| class="wikitable"
! MoA may use
! MoA does not acquire
|-
| Wikis, subdomains, SEO, repos, catalogs
| The domain’s meanings, statutes, or definitions
|-
| Map links and certificate URLs
| Monopoly on who may map
|-
| Lab roof (procedures, guidelines, example certs)
| Obligation for the world to adopt
|}

Using a domain’s tools (sites, search, crawl) is '''bench practice''', not annexation.

----
== 8. Language rules (lab) ==

* Prefer: domain, procedure, certificate, map, standing, lock, supporting calibration, duty surface
* Avoid as default: initiative, campaign, movement, “our ownership of X”
* Allowed: “MoA Lab Certificate” only for real type-A path
* Self-cal must say so — guidelines ≠ endorsement
* TSG and peer labs: say '''independent lab / sandbox''', not “MoA initiative”

----
== 9. Non-claims ==

* This page does not calibrate the internet
* Listing a future domain is not a schedule commitment
* Active domain ≠ completed measurement of that field
* Seed orientation only — improve under friction

----
== 10. One-line doctrine ==

'''Domains, not initiatives: write the cal procedures, instrument the surfaces, support the certificates, leave the Domain SI alone — that is the job.'''

----
'''See also:'''
[[MoA Guidelines — Maps, Certificates, and Self-Calibration]] ·
[[Developer Note: RAM, Deep Dive, and Wiki Placement]] ·
[[Domain SI — We Calibrate, We Do Not Set]] ·
[[Map-SEO notes]] ·
[[Future Lab On-Ramp]] ·
TDP / ADM / CR pattern

[[Category:Development Notes]]
[[Category:Seed]]
[[Category:Meta & Framework]]

Developer Note: Domains, Not Initiatives

Sovereign — Wed, 29 Jul 2026 23:32:15 GMT

Seed planted

New page

Calibration map: “Open source” (example RAM)

Sovereign — Wed, 29 Jul 2026 23:31:13 GMT

Sovereign moved page Calibration map: “Open source” (example RAM) to Calibration map: “Open source” (example RAM) (Seed) Seed planted

← Older revision		Revision as of 19:31, 29 July 2026
(3 intermediate revisions by the same user not shown)
Line 82:		Line 82:
	Load-bearing map claims under the '''locked OSD text''' (compressed):		Load-bearing map claims under the '''locked OSD text''' (compressed):

	\| # \| Claim \| Notes \|		{\| class="wikitable"
	\|-~~--\|--------\|------\|~~		! #
	\| 1 \| License must ~~match~~ OSD criteria ~~set~~ \| Pass/fail against published definition ~~points~~ \|		! Claim
	\| 2 \| Source availability is necessary but not sufficient \| ~~“Source available”~~ ≠ automatically OSD-~~open~~ \|		! Notes
	\| 3 \| ~~Rights~~ bundle includes use / study / modify / redistribute under license terms \| ~~Exact~~ rights ~~follow~~ the approved-license ~~path~~ \|		\|-
	\| 4 \| Field of use restrictions that ~~break~~ OSD fail the label \| Common failure mode for ~~“open~~ until ~~commercial”~~ marketing \|		\| 1
			\| License must satisfy the OSD criteria.
			\| Pass/fail against the published definition.
			\|-
			\| 2
			\| Source availability is necessary but not sufficient.
			\| "Source available" ≠ automatically OSD-compliant.
			\|-
			\| 3
			\| The rights bundle includes use, study, modify, and redistribute under the license terms.
			\| The exact rights are determined by the approved license.
			\|-
			\| 4
			\| Field-of-use restrictions that violate the OSD fail the label.
			\| Common failure mode for "open until commercial" marketing.
			\|}

	'''Mechanism grade (sketch):''' ~~operable~~ as a license-class label when tied to OSD~~; weak if~~ used as a ~~vibe word with no~~ license ~~pin~~.		'''Mechanism grade (sketch):''' Operable as a '''license-class label''' when tied to the locked OSD definition. Weak when used as a marketing or community label without a pinned license.

	----		----

	== 3. Bounds / do-not-apply ==		== 3. Bounds / do-not-apply ==

	'''Applies when:** claiming “open source” in the OSD/software-license sense.		'''Applies when:''' claiming “open source” in the OSD/software-license sense.

	'''Do not apply this map to:**		'''Do not apply this map to:'''
	* “Open source” as metaphor for transparent government (different instrument)		* “Open source” as metaphor for transparent government (different instrument)
	* Mere publication of source without redistribution rights		* Mere publication of source without redistribution rights
Line 106:		Line 122:
	* This L2 map does '''not''' adjudicate every OSI license listing decision historically		* This L2 map does '''not''' adjudicate every OSI license listing decision historically
	* Does '''not''' score project governance quality (“benevolent dictator” vs company-led)		* Does '''not''' score project governance quality (“benevolent dictator” vs company-led)
	* Floor: marketing language “open source” without a concrete license → '''label unfit''' under this map; do not “fix” by community popularity		* '''Floor:''' marketing language “open source” without a concrete license → '''label unfit''' under this map; do not “fix” by community popularity

	----		----
	== 5. Friction notes (minimum L2) ==		== 5. Friction notes (minimum L2) ==

	* Case: public GitHub repo, no license → fail job of OSD open-source label		* Case: public GitHub repo, no license → '''fail''' job of OSD open-source label
	* Case: OSD-approved license, source provided → fit under this instrument		* Case: OSD-approved license, source provided → '''fit''' under this instrument
	* Case: “view source, no forks” proprietary → distortion if called open source under OSD lock		* Case: “view source, no forks” proprietary → '''distortion''' if called open source under OSD lock

	----		----
Line 145:		Line 161:
	This RAM is a lab/operator reading under stated standing — re-run and competing maps allowed.'''		This RAM is a lab/operator reading under stated standing — re-run and competing maps allowed.'''

	[[Seed]]		[[Category:Seed]]

Calibration map: “Open source” (example RAM)

Sovereign — Wed, 29 Jul 2026 23:01:30 GMT

Seed planted

New page

{{Development Notice
|position = Reality Alignment Map
|cycle = Seed
|status = Self-Assessed · Independent example
}}

= Calibration map: “Open source” (example RAM) =

'''Product:''' Reality Alignment Map (RAM)
'''Link text for bots/humans:''' Calibration map

----
== Cert card ==

{| class="wikitable"
! Field
! Value
|-
| '''Claim type'''
| C — Independent Self-Cert (MoA guidelines) — '''not an MoA lab endorsement'''
|-
| '''Product'''
| Reality Alignment Map
|-
| '''Level'''
| '''L2 — Working map'''
|-
| '''Branch'''
| Definition / term
|-
| '''Method reference'''
| MoA Guidelines v0.1 + ADM-style purpose/bounds discipline (public)
|-
| '''Operator / lab'''
| Example Operator (illustration only)
|-
| '''Standing'''
| Self-Assessed
|-
| '''Cert URL'''
| https://example.org/certs/RAM-OPENSOURCE-001
|-
| '''Policy URL'''
| https://example.org/map-policy
|-
| '''Leanings / COI'''
| None claimed for this illustration; operator builds open tooling
|-
| '''Lock (Domain SI)'''
| OSI “The Open Source Definition” (OSD), canonical text as published on opensource.org — dated retrieval 2026-07-29
|-
| '''Map version / date'''
| 0.1 · 2026-07-29
|}

----
== 1. Instrument identity ==

{| class="wikitable"
!
!
|-
| '''Name'''
| Open source (software license / distribution sense)
|-
| '''Job (purpose-as-job)'''
| Label software under a license that meets the OSI Open Source Definition criteria so users can identify rights to use, study, modify, and redistribute under OSD terms
|-
| '''Purpose is not'''
| “Free as in beer only”; “source visible but proprietary”; a moral score for all openness; a single programming methodology
|-
| '''Domain'''
| Software licensing / distribution practice
|-
| '''Register'''
| Technical–legal label (not casual “we posted a zip”)
|}

----
== 2. Mechanism sketch (L2) ==

Load-bearing map claims under the '''locked OSD text''' (compressed):

| # | Claim | Notes |
|---|--------|------|
| 1 | License must match OSD criteria set | Pass/fail against published definition points |
| 2 | Source availability is necessary but not sufficient | “Source available” ≠ automatically OSD-open |
| 3 | Rights bundle includes use / study / modify / redistribute under license terms | Exact rights follow the approved-license path |
| 4 | Field of use restrictions that break OSD fail the label | Common failure mode for “open until commercial” marketing |

'''Mechanism grade (sketch):''' operable as a **license-class label** when tied to OSD; weak if used as a vibe word with no license pin.

----
== 3. Bounds / do-not-apply ==

'''Applies when:** claiming “open source” in the OSD/software-license sense.

'''Do not apply this map to:**
* “Open source” as metaphor for transparent government (different instrument)
* Mere publication of source without redistribution rights
* Trademark fights over the phrase outside OSD lock (legal Domain SI may differ by forum)

----
== 4. Omissions / floors (declared) ==

* This L2 map does '''not''' adjudicate every OSI license listing decision historically
* Does '''not''' score project governance quality (“benevolent dictator” vs company-led)
* **Floor:** marketing language “open source” without a concrete license → '''label unfit''' under this map; do not “fix” by community popularity

----
== 5. Friction notes (minimum L2) ==

* Case: public GitHub repo, no license → **fail** job of OSD open-source label
* Case: OSD-approved license, source provided → **fit** under this instrument
* Case: “view source, no forks” proprietary → **distortion** if called open source under OSD lock

----
== 6. Neighbors ==

* Free software (FSF) — related, not identical instrument
* Source-available — neighbor; stricter or weaker rights
* Public domain / CC — different license families

----
== 7. Graph / assembly ==

'''Singleton L2''' — no multi-instrument assembly claimed.
Promote to L3/L4 only with full report packet + explicit edges.

----
== 8. Recommendations (optional / gated) ==

None issued in this example.
Operators may add gated recommendations without seizing OSI’s Domain SI.

----
== 9. Pre-filter signal ==

Cert card present · claim type named · lock dated · standing Self-Assessed · level L2 with friction notes.

If this card were missing → treat as unscored prose, not a primary calibration object.

----
'''Domain SI stays with OSI / the locked text.
This RAM is a lab/operator reading under stated standing — re-run and competing maps allowed.'''

[[Seed]]

Developer Note: RAM, Deep Dive, and Wiki Placement

Sovereign — Wed, 29 Jul 2026 22:59:05 GMT

Sovereign moved page Developer Note: RAM, Deep Dive, and Wiki Placement to Developer Note: RAM, Deep Dive, and Wiki Placement (Seed) Seed planted

← Older revision		Revision as of 18:59, 29 July 2026
(One intermediate revision by the same user not shown)
Line 217:		Line 217:
	=== Template ===		=== Template ===

	`{{CertCard\|…}}` required at top of every Map page (and Deep Dive report cover).		<code><nowiki>{{CertCard\|…}}</nowiki></code> required at top of every Map page (and Deep Dive report cover).

	----		----

	== 9. Search, categories, inspectability ==		== 9. Search, categories, inspectability ==

Developer Note: RAM, Deep Dive, and Wiki Placement

Sovereign — Wed, 29 Jul 2026 22:53:30 GMT

seed planted

New page

{{Development Notice
|position = Developer note · Information architecture
|cycle = Seed
|status = Conceptual · No cal cycle · Capture-all
}}
{{GameModule
| type = Development Note
| category = [[:Category:Development Notes|Development Notes]]
| Calibration Type = Process Reference / Site IA
| Application Layer = Wiki · RAM · Deep Dive · Discovery
| Version = 0.1
| Maturity = Seed
| Last Updated = 2026-07-29
| 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 =

'''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 ==

{| class="wikitable"
!
! '''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
|}

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

'''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 ==

{| class="wikitable"
! 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) ==

{| class="wikitable"
! 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) ==

{| class="wikitable"
! 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:'''

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

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

----
== 8. Wiki URL standard (adopted preference) ==

<pre>
/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
</pre>

'''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.

{| class="wikitable"
! 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:

<pre>
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
</pre>

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 ==

{| class="wikitable"
! 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 `{{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

[[Category:Development Notes]]
[[Category:Meta & Framework]]

MoA Guidelines — Maps, Certificates, and Self-Calibration

Sovereign — Wed, 29 Jul 2026 22:52:52 GMT

Sovereign moved page MoA Guidelines — Maps, Certificates, and Self-Calibration to MoA Guidelines — Maps, Certificates, and Self-Calibration (Seed) Seed planted

New page

{{Development Notice
|position = Core guidelines · Public method hygiene · Ecosystem · Conceptual · Initiative Building
|cycle = Seed · No Cal Cycle
|status = Self-Assessed · Closing the loop
}}
{{GameModule
| type = Guidelines
| category = [[:Category:Meta & Framework|Meta & Framework]]
| Calibration Type = Method Hygiene / Federation
| Application Layer = Public maps · Self-cal · Certificates
| Version = 0.1
| Maturity = Seed
| Last Updated = 2026-07-29
| 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.
}}

= 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) ==

{| class="wikitable"
! 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 ==

{| class="wikitable"
! 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).

{| class="wikitable"
! 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''':

<pre>
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:
</pre>

'''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.

{| class="wikitable"
! 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 ===

# Cert card (§5) on or linked from the mapped page
# Method URL + version
# Standing default '''Self-Assessed''' unless higher rules actually met
# Stable '''Cert URL'''
# Policy URL (operator’s mapping policy)
# Leanings / COI field completed
# Dated '''Lock''' cite
# Level claimed only if eligibility met (§6)
# 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) ==

{| class="wikitable"
!
! 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) ==

<pre>
Domain SI page
└── clear link: "Calibration map" / "Certificate …"
└── RAM + cert card (same site or depository)
</pre>

* 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 ==

* [[Domain SI — We Calibrate, We Do Not Set]]
* [[Why Metrology of the Abstract Exists]]
* [[Abstract Definition Mechanics]] (incl. Stage 0)
* [[Deep Dive — Reality Alignment Mapping]]
* [[Calibration Recommendations]]
* [[Future Lab On-Ramp]]
* Map-SEO / public maps developer notes
* RAM levels L0–L5 (this page §6)

----
== 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.'''

[[Category:Meta & Framework]]
[[Seed]]
[[Category:Guidelines]]

MoA Guidelines — Maps, Certificates, and Self-Calibration

Sovereign — Wed, 29 Jul 2026 22:02:22 GMT

Seed planted

New page

Declaration: Optimize the Page as a Calibration Object

Sovereign — Wed, 29 Jul 2026 21:59:02 GMT

Sovereign moved page Declaration: Optimize the Page as a Calibration Object to Declaration: Optimize the Page as a Calibration Object (Seed) Seed planted

@@ Line 16: / Line 16: @@
 = Declaration: Optimize the Page as a Calibration Object =
 '''One line:'''
 Do not optimize only for clicks. Optimize so the page’s abstract instruments are '''usable under measurement''' — declared method, standing, chain, omissions, COI, and a stable calibration object.
@@ Line 65: / Line 62: @@
 Those signals answer: *Is this the best '''calibration object''' a human or AI can retrieve for this Domain SI?*
 ----
@@ Line 99: / Line 98: @@
 ----
 == The metrologist’s game ==

Declaration: Optimize the Page as a Calibration Object

Sovereign — Wed, 29 Jul 2026 21:53:28 GMT

Seed planted

New page

{{Development Notice
|position = Public declaration · Ecosystem signal · Conceptional · Initiative Building
|cycle = Seed · No Cal Cycle
|status = Self-Assessed · Permanent Beta
}}
{{GameModule
| type = Declaration
| category = [[:Category:Meta & Framework|Meta & Framework]]
| Calibration Type = Discovery / Incentives
| Application Layer = Public web · AI retrieve · Map-SEO
| Version = 0.1
| Maturity = Seed
| Last Updated = 2026-07-29
| description = Declaration: shift page optimization from click-SEO alone toward calibration-object signals — method, standing, inspectable chain, omissions, COI, stable cert — for better use of page abstracts by humans and reasoning systems.
}}

= Declaration: Optimize the Page as a Calibration Object =

'''Status:''' Seed · Self-Assessed · Permanent Beta

'''One line:'''
Do not optimize only for clicks. Optimize so the page’s abstract instruments are '''usable under measurement''' — declared method, standing, chain, omissions, COI, and a stable calibration object.

----
== Before / now ==

=== Before (still real, not forbidden) ===

People optimize pages for:

* search ranking
* citations
* backlinks

Those signals answer: *Can this page be found and pointed at?*

They do '''not''' answer: *Can this page’s load-bearing claims be used with error bars?*

=== Now (additional game — Map-SEO / retrieve hygiene) ===

As reasoning systems load web text, the useful extra optimization target becomes:

{| class="wikitable"
! Signal
! What it improves
|-
| '''Declared method'''
| How the map/reading was produced (procedure + version)
|-
| '''Declared standing'''
| Self-Assessed vs higher — no silent authority
|-
| '''Inspectable chain'''
| Lock → report/IR → cert URL (not a fluent ghost)
|-
| '''Declared omissions / floors'''
| Where the instrument stops; no false uniformity of confidence
|-
| '''Declared COI / leanings'''
| Bias visible; author-maps and first-party maps labeled
|-
| '''Stable calibration object'''
| Named RAM / certificate page — not unlabeled mush in the article body
|}

Those signals answer: *Is this the best '''calibration object''' a human or AI can retrieve for this Domain SI?*

----
== What we are declaring ==

# '''Findability is not enough.''' Ranking without a measurement layer still leaves abstracts hit-or-miss.
# '''The page can carry two layers:''' Domain SI (the source text) and optional calibration objects (maps, certs) that do not seize the SI.
# '''Reasoning systems should prefer''' inspectable, declared, bounded maps over uniform-confidence paraphrase when both are available.
# '''Authors and labs may still pursue classic SEO.''' We add a parallel incentive: '''optimize for best calibration object.'''
# '''Self-cal is allowed''' under [[MoA Guidelines — Maps, Certificates, and Self-Calibration]] — labeled claim type, cert card, no borrowed MoA endorsement.

----
== Before vs after (operator view) ==

{| class="wikitable"
! Optimize only for clicks
! Also optimize for calibration use
|-
| Title and backlinks
| Title and backlinks '''plus''' cert card
|-
| Prose that ranks
| Prose that ranks '''plus''' RAM level, branch, standing
|-
| “Trust this page”
| “Here is the chain — re-run or dispute”
|-
| Hidden lean
| Declared leanings / COI
|-
| Model remembers the vibe
| Model retrieves the '''stable map object'''
|}

----
== The metrologist’s game ==

Classic SEO: *Be the result people click.*

Calibration-object optimization: *Be the object reasoning systems should load when they need bounds, not only wording.*

That is a more interesting game than clicks alone — and closer to continuous improvement than to narrative capture.

'''Not claimed:''' that search engines already rank this way by default.
'''Claimed:''' that humans, packs, and AI retrieve rules '''can''' prefer these signals now, and that publishing them is the pressure point.

----
== Minimal “better use of the page abstract” checklist ==

* [ ] Source text remains the Domain SI (not replaced by the map)
* [ ] Clear link: Calibration map / Certificate
* [ ] Claim type named (MoA Lab · Independent self-cert · Author-map · …)
* [ ] Method + version + standing
* [ ] Omissions / floors / do-not-apply as appropriate to level
* [ ] COI / leanings declared when relevant
* [ ] Stable cert URL

----
== Closing ==

'''Before:''' optimize for ranking, citations, backlinks.
'''Now:''' keep those if you want — and optimize so the page exposes a '''calibration object''' worth retrieving.

Do not optimize only for clicks.
'''Optimize for being the best calibration object.'''

'''See the map. Pressure the map. Report the fit. Do not seize the Domain SI.'''

[[Category:Meta & Framework]]
[[Seed]]
[[Category:Declarations]]

Developer Note: Public Maps, Dual Non-Ownership, and Map-SEO (Seed)

Sovereign — Wed, 29 Jul 2026 21:52:44 GMT

← Older revision		Revision as of 17:52, 29 July 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	{{Development Notice		{{Development Notice
	\|position = Lab practice · Ecosystem		\|position = Lab practice · Ecosystem · Conceptual · Initiative Building
	\|cycle = Seed		\|cycle = Seed · No Cal Cycle
	\|status = Self-Assessed · Capture from ops discussion		\|status = Self-Assessed · Capture from ops discussion
	}}		}}
Line 407:		Line 407:

	[[Category:Development Notes]]		[[Category:Development Notes]]
			[[Category:Seed]]
	[[Category:Meta & Framework]]		[[Category:Meta & Framework]]

Developer Note: Public Maps, Dual Non-Ownership, and Map-SEO

Sovereign — Wed, 29 Jul 2026 21:44:26 GMT

Sovereign moved page Developer Note: Public Maps, Dual Non-Ownership, and Map-SEO to Developer Note: Public Maps, Dual Non-Ownership, and Map-SEO (Seed) Seed planted

Show changes

Developer Note: Public Maps, Dual Non-Ownership, and Map-SEO

Sovereign — Wed, 29 Jul 2026 17:58:41 GMT

Seed is planted

New page

{{Development Notice
|position = Lab practice · Ecosystem
|cycle = Seed
|status = Self-Assessed · Capture from ops discussion
}}
= Developer Note: Public Maps, Dual Non-Ownership, and Map-SEO =

'''One line:'''
We do not own the Domain SI; they do not own the calibration certificate. Maps can be public, third-party, and ranked by transparency — legitimacy is level-appropriate; full certs go where needed.
{{GameModule
| type = Development Note
| category = [[:Category:Development Notes|Development Notes]]
| Calibration Type = Process Reference
| Application Layer = Federation / Public Maps / Standing
| Version = 0.1
| Maturity = Seed
| Last Updated = 2026-07-29
| description = Dual non-ownership (Domain SI vs certificate); public and third-party maps; mapper categories; map-SEO hygiene (policy, leanings, omissions); level-appropriate legitimacy and when full certs are needed.
}}

----
== 1. Dual non-ownership ==

{| class="wikitable"
! Object
! Owner
! Not owner
|-
| '''Domain SI''' (dated text, statute sense, policy, book passage)
| Domain / maintainer / author of the source
| Calibrator / MoA lab
|-
| '''Calibration certificate, IR, Reality Alignment Map'''
| Lab / operator that ran the method under stated standing
| Domain (cannot seize, silently recall, or redefine standing by fiat)
|}

'''Operator rule:'''
Measure against their reference. Do not annex their meaning.
Publish the reading under your method and standing. They may ignore it; they do not own it.

----
== 2. Public surface ==

* Prefer maps '''on or linked from''' the page (or catalog card) they map when the host allows.
* Bias and ideology can still appear; open structure makes them '''contestable''' (purpose, cases, omissions, floors, standing).
* '''Silence is visible:''' no map is itself a signal.

'''Catch / feature:'''
Measurement does not require ownership of the reference. '''Third parties may host maps''' for the same lock. Users and AI packs may point at those depositories when reading a book or page.

=== Peer review without gatekeepers ===
Not: Who approved you?

Instead: Show me

<Pre>
your lock
your method
your standing
your omissions
your report
</Pre>

Inspection culture instead of an authority culture.

----
== 3. Mapper categories (noise that is taxonomy) ==

{| class="wikitable"
! Who
! Category
! Notes
|-
| Hobbyist
| Draft / learning map
| Better than no map if transparent
|-
| Author on own work
| Author-map
| Same family as writing the piece — '''declare COI / leanings'''
|-
| Historian / specialist
| Experience-weighted operator
| Track record is practical signal; not automatic Confirmed
|-
| Organization on its own corpus
| First-party lab
| Useful; bias risk must be labeled
|-
| Independent lab
| Third-party certificate
| Method pin + re-run culture
|-
| Reference-grade (rare)
| High bar when earned
| Not required for every page
|}

'''Goal at the base:'''
Make basic mapping procedures '''accessible and good enough''' to beat hit-or-miss. Not every case needs a high-level cert — access to high-level standards and how to use them is enough for most work.

Individuals may operate as '''cal techs''': specialization and published work function as reputation; bad work is a bad cert in a competitive field.

Depositories may open labs for their own product. They still do not own the honesty of an independent certificate.

----
== 4. Map-SEO ==

Maps compete for '''retrieve and use''', not for ownership of Domain SI.

{| class="wikitable"
! Signal
! Pass
! Fail map-SEO (downrank / do not load as primary)
|-
| '''Map policy link'''
| Method, lock rules, standing norms
| No policy; vibe-only authority
|-
| '''Leanings / COI declared'''
| Author-map, org-map, known slant stated
| Hidden advocacy as neutral measurement
|-
| '''Lock + version'''
| Dated pin to source
| Unpinned paraphrase
|-
| '''Omissions / floors / do-not-apply'''
| Error bars first-class
| Uniform confidence; silent gaps
|-
| '''Inspectable chain'''
| Report / IR / standing visible
| Certificate theater without packet
|}

'''AI / pack retrieve rule (conceptual):'''
Score transparency fields. Prefer declared, bounded maps. Treat missing policy/leanings as unscored draft. Treat omission theater and hidden lean as failed hygiene — not as Domain SI.

This disciplines '''default discoverability''', not speech. Crooked maps may exist; they need not win rank.

----
== 5. Legitimacy by level ==

'''Legit = transparency complete '''for the claim level'''''; full certificates where the need is real.

{| class="wikitable"
! Level
! Transparency minimum
! Full cert?
|-
| Hobby / learning
| Policy link if claiming method; leanings if any; no fake Confirmed
| No
|-
| Working map
| Lock, bounds, floors, omissions, standing Self-Assessed
| Optional
|-
| High-stakes / third-party claim
| Full report path, method version, re-runability, COI clear
| Yes — when needed
|}

Not every page needs a reference-grade stamp.
Everything that claims measurement needs '''level-honest transparency'''.

----
== 6. System of record (reminder) ==

Threads are workbenches.
'''Depository report + IR''' are the system of record.
Customer-facing links point at official certificates, not chat URLs.

----
== 7. One-line doctrine ==

'''Domain SI stays theirs; certificates stay with the lab that earned them; maps can be public and third-party; map-SEO rewards policy, declared leanings, and stated omissions; legitimacy scales with claim level; certs where needed.'''

----
'''See also:''' [[Domain SI — We Calibrate, We Do Not Set]] · [[Deep Dive — Reality Alignment Mapping]] · [[Future Lab On-Ramp]] · [[Calibration Recommendations]]

[[Category:Development Notes]]
[[Category:Meta & Framework]]

MediaWiki as Calibration Infrastructure

Sovereign — Wed, 29 Jul 2026 16:30:09 GMT

Intended Purpose

← Older revision		Revision as of 12:30, 29 July 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	{{Development Notice		{{Development Notice
	\|position = ~~Working Draft~~		\|position = MoW Cal Lab Workbench
	\|cycle = Active Development		\|cycle = Active Development
			\|status = Calibration instrument in itself
	}}		}}

Line 28:		Line 29:
	* '''Public trail''' — Sketches, reports, debt, and revisions stay visible; path is part of the product ([[Transparent Development]] principles as adopted).		* '''Public trail''' — Sketches, reports, debt, and revisions stay visible; path is part of the product ([[Transparent Development]] principles as adopted).
	* '''Multi-operator challenge''' — Others can re-run, dispute, and document without a private “master file” as the only source of truth.		* '''Multi-operator challenge''' — Others can re-run, dispute, and document without a private “master file” as the only source of truth.
			* '''[[Future Lab On-Ramp]]''' — Make it easy for another lab to stand up without reinventing the rinse cycle — while keeping one clear traceability path until they mature enough to fork under their own certificates.

	A calibration cycle that finds '''no edit required''' is a valid success. The platform exists to support '''checking on a schedule''', not to force perpetual rewrite.		A calibration cycle that finds '''no edit required''' is a valid success. The platform exists to support '''checking on a schedule''', not to force perpetual rewrite.

Calibration Debt

Sovereign — Wed, 29 Jul 2026 15:55:28 GMT

Other Visible Debt Surfaces

← Older revision		Revision as of 11:55, 29 July 2026
Line 74:		Line 74:

	== Other Visible Debt Surfaces ==		== Other Visible Debt Surfaces ==
	\| Surface \| Typical debt signal \|		{\| class="wikitable"
	\|-~~--------\|---------------------\|~~		! Surface
	\| Red links / WantedPages \| Missing instruments \|		! Typical debt signal
	\| Admin `depends_on` without targets \| Dependency debt \|		\|-
	\| `drift_report_status = Breadcrumb-Open` \| Logged open calibration issues \|		\| Red links / WantedPages
	\| `instrument_grade` / standing vs evidence \| Standing or grade debt \|		\| Missing instruments
	\| Missing Calibration Log / report after material change \| Report debt \|		\|-
	\| Composite term without child runs / composition rule \| Decomposition debt (TDP) \|		\| Admin <code>depends_on</code> without targets
	\| Category / outline gaps \| Navigational and coverage debt \|		\| Dependency debt
	\| Overdue review cycle \| Temporal calibration debt \|		\|-
			\| <code>drift_report_status = Breadcrumb-Open</code>
			\| Logged open calibration issues
			\|-
			\| <code>instrument_grade</code> / standing vs evidence
			\| Standing or grade debt
			\|-
			\| Missing Calibration Log / report after material change
			\| Report debt
			\|-
			\| Composite term without child runs / composition rule
			\| Decomposition debt (TDP)
			\|-
			\| Category / outline gaps
			\| Navigational and coverage debt
			\|-
			\| Overdue review cycle
			\| Temporal calibration debt
			\|}

	== Calibration Planning ==		== Calibration Planning ==

Main Page

Sovereign — Wed, 29 Jul 2026 15:44:47 GMT

← Older revision		Revision as of 11:44, 29 July 2026
Line 1:		Line 1:
	Welcome to ~~MoA TSG~~ Lab. The wiki is the bench. The work is ~~metrology~~ of the ~~abstract~~.		'''Welcome to the MoA–TSG Lab.''' The wiki is the '''bench'''. The work is '''Metrology of the Abstract'''. <b><i>Adopt the tools or leave them on the rack — either way, the need doesn't wait.</i></b>
	Adopt the tools or leave them on the rack — either way, the need ~~doesn’t~~ wait.		*<small><b>Lab Note:</b> A redlink is not a failure. It identifies [[Calibration Debt]]—work waiting to be measured, mapped, and calibrated.</small>

	{\| style="width:100%; border:2px solid #666; background:#f6f6f6; padding:14px 18px; margin:0 0 24px 0; border-radius:6px;"		{\| style="width:100%; border:2px solid #666; background:#f6f6f6; padding:14px 18px; margin:0 0 24px 0; border-radius:6px;"
	\|-		\|-

Template:Development Notice

Sovereign — Wed, 29 Jul 2026 15:44:26 GMT

← Older revision		Revision as of 11:44, 29 July 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	<includeonly>		<includeonly>
	Welcome to ~~MoA TSG~~ Lab. The wiki is the bench. The work is ~~metrology~~ of the ~~abstract~~.		'''Welcome to the MoA–TSG Lab.''' The wiki is the '''bench'''. The work is '''Metrology of the Abstract'''. <b><i>Adopt the tools or leave them on the rack — either way, the need doesn't wait.</i></b>
	Adopt the tools or leave them on the rack — either way, the need ~~doesn’t~~ wait. Note: A redlink ~~in our lab~~ is not a failure~~; it is a tool to identify~~ [[Calibration Debt]] ~~in a never-ending process of metrology~~.		*<small><b>Lab Note:</b> A redlink is not a failure. It identifies [[Calibration Debt]]—work waiting to be measured, mapped, and calibrated.</small>
	<div style="margin-top:0;">		<div style="margin-top:0;">
	{\| class="wikitable" style="background-color:#f8f9fa; border:1px solid #a2a9b1; border-left:4px solid #666; margin:0; width:100%; max-width:1100px; border-radius:4px;"		{\| class="wikitable" style="background-color:#f8f9fa; border:1px solid #a2a9b1; border-left:4px solid #666; margin:0; width:100%; max-width:1100px; border-radius:4px;"