Sovereign at 23:33, 29 July 2026

2026-07-29T23:33:20Z

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

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

2026-07-29T23:32:41Z

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

← Older revision	Revision as of 19:32, 29 July 2026
(No difference)

Sovereign: Seed planted

2026-07-29T23:32:15Z

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 (Seed) - Revision history

Sovereign at 23:33, 29 July 2026

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

Sovereign: Seed planted