# Realm Intelligence Contract — 2nd Cavalry Living History, Service, and Connection System

**Status:** Gate 2A working definition; not an adopted 2nd Cavalry Association or Service Alliance plan  
**Canonical basis:** Version 1.3.3  
**Source handling:** The SADUNA backbrief is confidential and remains proposed/unverified  
**Primary unresolved items:** C-001–C-005, C-015–C-019

## 1. Evidence boundary

### Source-backed domain evidence

The Dragoon Base concept paper reports a substantial, long-lived community archive organized around **History, Service, and Connection**. Its March 17, 2026 archive claims 4,377 member profiles, 14,567 photographs, 126 videos, and 68+ groups, with materials spanning unit locations, eras, battles, reunions, memorials, benefits, memoirs, and personal connection. The market report separately cites a public Dragoon Base count of 3,192. The conflict is preserved as C-001.

The concept paper proposes interactive history, oral-history capture, benefits navigation, trauma-informed support, mutual aid, leadership learning, persistent memory, multi-Surface continuity, and migration from Ning. These are proposals supported by observed needs, not implemented capabilities.

The [Library of Congress Veterans History Project](https://www.loc.gov/vets/fieldkit-guidelines.html) provides a primary model for release forms, interviewer records, media standards, and collection logs. Current [VA guidance](https://www.publichealth.va.gov/exposures/gulfwar/medically-unexplained-illness.asp) preserves uncertainty around Gulf War illness terminology and points veterans to benefits, research, and professional evaluation.

### Confidential proposed evidence

The SADUNA backbrief proposes relationships among Service Alliance LLC, SADUNA, and Kiduna Club, along with identity, governance, Treasury, founder, and tool structures. The document explicitly asks for confirmation and provides no executed legal evidence. Gate 2A uses it only to identify possible Realm relationships and authority questions. Public scene briefs may not reveal its unreleased launch, founder, financial, or legal mechanics (C-003, C-004, C-019).

## 2. Proposed relationship graph

This is not one undifferentiated Realm.

```text
2nd Cavalry Association — established external organization; exact canonical Realm type unresolved (C-004)
├── Dragoon Base — legacy hosted Community/archive source, not the Association itself
├── Trooper–Veteran Connection Community Realms
├── Living History Alliance/Program [working structure]
│   ├── Oral History Program Realm
│   ├── Archive Preservation Project Realm
│   ├── Battle of Palo Alto Project + possible Scene
│   ├── Battle of 73 Easting Project + possible Scene
│   ├── Cold War Border Project + possible Scene
│   └── Memorial / Fiddler's Green Realm
└── Service and Connection Program Realms
    ├── benefits and records navigation
    ├── peer connection and mutual aid
    ├── gatherings and reunions
    └── leadership learning

Possible external relationships [all require confirmation]
├── Service Alliance LLC — proposed sponsor/service/IP Realm
├── SADUNA — proposed member-governed Organization Realm; legal status unverified
└── Kiduna Club — proposed protocol/substrate Organization Realm
```

An Association decision would be required to establish actual ownership, governance, sponsorship, data custody, or service relationships.

## 3. Complete Realm contract

| Dimension | Definition | Evidence or proposal |
|---|---|---|
| Name and purpose | The **2nd Cavalry Living History, Service, and Connection system** preserves and activates regimental memory, connects current troopers and veterans, supports trustworthy service navigation and human mutual support, and allows history to keep growing through governed contribution. | DB + owner direction |
| Audience | Veterans, current troopers, family members, historians, archivists, Association members/leaders, volunteers, donors, researchers, educators, and authorized service professionals. Visitors see only explicitly public history. | DB + WP |
| Promised outcomes | Durable oral histories; searchable and attributable archive; interactive evidence-bounded history; connection across eras/places; trustworthy routing to benefits and human help; gatherings that persist as memory; correction and contested-account support. | DB + OD |
| Non-goals | Generic social feed; replacement for the Association; fabricated historical authority; autonomous publication of sensitive service information; diagnosis, legal representation, accredited claims representation, emergency/crisis replacement, facial identification without policy/consent, or forced migration. | Safety boundary + WP |
| Wisdom | Original archive; photographs/videos; oral histories; official records, citations, unit diaries, after-action reports, maps; scholarly interpretation; Association decisions; contributor annotations; current VA/benefits sources; service-provider directories. Each class remains distinct. | DB + LOC/VA + WP |
| Stance | Toujours Prêt; dignified, nonpartisan, service-oriented, trauma-aware, veteran-controlled, source-visible, humble about contested memory, protective of active-duty/sensitive information, and committed to connecting rather than extracting. | DB + SA-MR + WP |
| Abilities | Preserve, transcribe, describe, index, search, compare, annotate, map, create source-bounded Scenes, conduct interviews, connect people by chosen service context, prepare benefit/service pathways, support gatherings, manage corrections and rights. | DB + WP |
| Automations | Ingest/index authorized archive; create draft transcripts/metadata; watch official benefit-source freshness; surface anniversary/source relationships; detect duplicates; prepare connection suggestions. No public face identification, health inference, credibility scoring, publication, or outreach without authority. | DB + WP |
| Connections | Ning/read-only archive, Association sites, CRM/email, approved media storage, official history repositories, Library of Congress/NARA-aligned resources, VA/benefits sources, streaming/communications, and other systems only under explicit custody and delegation. | DB + SA-MR + WP |
| Actors | Ki; Archive Migration Operator; Oral History Interview Worker; Transcription/Metadata Worker; Historical Source Sentinel; Scene Composer; Benefits Navigation Worker; Peer Connection Actor; Privacy/Rights Sentinel; Editorial Supervisor; Institution Integration Actors. | WP |
| Elements | Profile/Presence, oral history, recording, transcript, photograph, video, map, official record, memoir, annotation, claim, contested account, event/gathering, memorial, benefits Source, connection proposal, Scene, Portal, Action, consent/release, rights record, correction, and receipt. | DB + WP |
| Roles and authority | Contributor controls offered testimony/material within release terms; veteran subject has Personal rights; interviewer performs bounded capture; archive steward manages custody; historian/editor interprets but cannot rewrite testimony; Association authority publishes/adopts official material; benefits professional acts only under actual credential/delegation; peer supporter offers human connection, not clinical care; sponsor/provider has no implied archive control. | WP |
| Privacy and visibility | Public, Association/member, group/unit/era, Relationship, Personal, Private, Secret, embargoed, memorial, and restricted-active-duty scopes may coexist. Service history, health, benefits, family, security-clearance, and operational details receive purpose-specific controls. Discovery may reveal existence without content. | T133 + DB + WP |
| Policies and gates | Private search/draft metadata may be Autonomous; contact or routine submission is Confirmed; publishing testimony, cross-linking identities, entering a sensitive Scene, or releasing health/service details is Deliberate; Association canon, memorial representation, archive migration, governance, and Treasury Actions are Governed; invented eyewitness speech, unauthorized disclosure, and unsupported clinical/legal representation are Prohibited. | T133 + WP |
| Default state | One active Project/Community/Program Realm, one Focus, one dominant conversation, and at most three relevant Sources/contributions. People appear through testimony, relationship, or needed authority rather than a permanent member wall. | AD-001–003 + OD |
| Attention states | Rights/consent conflict; contested identification; sensitive operational or health detail; conflicting eyewitness accounts; Source/reconstruction exceeds evidence; vulnerable veteran asks for urgent help; benefits source changed; archive migration mismatch; memorial dispute; required Association authority; failed external Action. | WP |
| Records | Release/consent; original-file hash and custody; interview log; transcript/annotation version; metadata provenance; rights/visibility; editorial decision; contested-account link; Scene source manifest/review; publication; disclosure; benefits referral; connection acceptance; correction/withdrawal; migration reconciliation. | LOC + WP |
| Recovery | Preserve originals; stop publication/migration on rights conflict; quarantine uncertain matches; restore prior metadata/version; separate testimony from interpretation; restrict sensitive material; route urgent needs to appropriate humans/services; record contested status; honor withdrawal within preservation/legal limits; appeal editorial decisions. | WP |
| Compute | Material for transcription, media analysis, Scene generation, and archive indexing. Show budget/limits when a large batch or Scene begins. Low Compute pauses/degrades nonessential processing but never skips provenance, privacy, rights, or editorial review. | T133 + WP |
| Treasury | Donations, memorials, grants, mutual aid, events, preservation, and paid Offerings may involve the owning Realm's Treasury. Financial authority follows Association/Realm governance; source documents' proposed SADUNA economics are not defaults. | T133 + DB; SA-C remains confidential proposal |

## 4. Actors and Sources of authority

| Actor | Represents | Source of authority | May | Must not |
|---|---|---|---|---|
| Ki | Current Presence | Presence instruction plus Realm permissions | Explore, explain, attach Sources, prepare contribution, suggest human connection | Reveal another veteran's private material or claim official voice |
| Archive Migration Operator | Association/archive-custodian Realm | Governed migration decision and custody agreement | Inventory, hash, transfer, reconcile, report exceptions | Assume rights, publish, delete, or promise completeness |
| Oral History Interview Worker | Contributor/interview Project | Contributor consent and interview protocol | Prepare questions, record, transcribe draft, collect metadata | Pressure disclosure, reinterpret testimony, expand release |
| Historical Source Sentinel | Living History Realm | Editorial policy and approved Sources | Check provenance, claims, dates, gaps, contested status | Declare one memory “true” by popularity |
| Scene Composer | Historical Project | Approved source set and editorial mandate | Build bounded reconstruction draft | Invent eyewitness knowledge or hide reconstruction |
| Benefits Navigation Worker | Veteran | Veteran instruction and current official Sources | Explain pathways, organize questions/documents, route to accredited/human support | Diagnose, promise eligibility, submit/represent without authority |
| Peer Connection Actor | Community/Relationship | Opt-in matching policy and member consent | Propose a connection based on chosen context | Expose health, private history, or identity without consent |
| Privacy/Rights Sentinel | Contributor/subject/Realm policy | Release, custody, privacy, and sensitive-data policy | Restrict, flag, block, log, route appeal | Grant rights or unilaterally destroy preservation records |
| Editorial Supervisor | Association/history Realm | Named editorial Role/governance | Accept interpretation, publication, Scene version, correction | Modify original testimony silently |

## 5. Living Archive contribution model

### Invariants

1. Original testimony and files remain distinguishable from transcripts, metadata, interpretation, and reconstruction.
2. An accepted contribution is not automatically an official Association position.
3. Conflicting memories remain attributable and linked rather than averaged.
4. A correction to metadata or interpretation never rewrites the original testimony.
5. Rights, release, chosen visibility, permitted use, and preservation terms travel with every representation.
6. AI-generated material is labeled and cannot become a primary Source merely through repetition.
7. Health and benefits discussions remain separate from public historical identity unless the veteran explicitly joins them under a valid purpose.

### Contribution pathways

| Contribution | Contributor / Source | Receiving scope | Visibility | Acceptance authority | Canonical effect | Retention / correction / Record |
|---|---|---|---|---|---|---|
| Oral history | Veteran/family under interview release | Personal draft → chosen group/Association/public | Contributor-selected + policy | Archive steward accepts collection; editorial authority curates | Primary testimony, not universal fact | Original preserved; transcript corrected by layer; release/withdrawal limits recorded |
| Photograph/video | Rights holder/custodian; original file | Archive/Project/Community | Rights- and subject-sensitive | Archive steward | Source Artifact when provenance sufficient | Hash, custody, caption versions, subject objections, takedown/restriction Record |
| Official record | Issuing Institution/repository | History Project/Association | Source policy | Historical Source Sentinel verifies representation | Authoritative for its issued claim, still interpretable/contestable | Citation, retrieval date, integrity, supersession |
| Eyewitness correction or conflicting memory | Attributed veteran | Linked to original claim/event | Chosen scope | Editorial steward links; does not select by popularity | Contested testimony set | Both preserved, relationship and editorial note recorded |
| Community annotation | Member with contextual knowledge | Group/Project candidate | Realm-defined | Archive/history steward | Candidate metadata until reviewed | Attribution, confidence, acceptance/rejection, correction |
| Benefits/health question | Veteran in private context | Personal/Relationship or chosen service Program | Personal + Private | Veteran and authorized human/service authority | No historical canon | Current official Sources, referral, consent, follow-up Record |
| Historical Scene | Scene Composer from approved source set | Project/Association/public as governed | Policy-defined | Editorial authority + rights/privacy review | Interpretation/reconstruction Artifact | Source manifest, gaps, versions, review, corrections, Portal |
| Memorial entry | Family/contributor/Association Source | Memorial Realm | Dignity/visibility policy | Memorial authority | Official memorial representation when governed | Evidence, consent, wording, dispute/appeal, preserved revisions |

## 6. Archive migration contract

“Nothing is lost” is an aspiration, not an accepted result (C-002/C-016). A valid migration has stages:

1. **Authority** — Association/archive custodian authorizes scope; terms with the legacy host are inspected.
2. **Inventory** — profiles, files, groups, posts, comments, events, links, permissions, deletions, and unavailable objects are counted separately.
3. **Preservation capture** — original bytes, timestamps, identifiers, relationships, and hashes are retained where lawful and available.
4. **Rights and sensitivity** — owner/custodian, subjects, releases, visibility, health/service sensitivity, minors/family, and active-duty risks are classified.
5. **Staging** — material enters a non-public migration Realm; uncertain identity matches and duplicates remain unresolved.
6. **Reconciliation** — source and destination counts, hashes, failures, transformed formats, and excluded material are reported.
7. **Member control** — contributors receive clear continuity, re-consent/restriction options where required, and correction paths.
8. **Release** — only governed collections become visible; the legacy system may coexist read-only until acceptance.
9. **Ongoing preservation** — integrity checks, format migration, custody changes, and takedown/correction Records continue.

No 48-hour or complete migration claim is accepted without this evidence.

## 7. Historical Scene contract

### Suitable Scene intents

- explore positions, movement, terrain, chronology, and Sources for Palo Alto or 73 Easting;
- compare documented accounts and after-action interpretations;
- locate oral histories, photographs, or unit experiences in place/time;
- participate in a memorial, reunion, or leadership simulation where the bounded environment matters.

### Required truth layers

1. **Primary/official Source** — visible citation and date.
2. **Attributed testimony** — speaker, context, release, and memory status.
3. **Scholarly/editorial interpretation** — author/reviewer and perspective.
4. **Reconstruction** — visual inference labeled by confidence.
5. **Unknown/contested** — shown as a gap or alternatives, not filled by AI.

### Prohibited behavior

- a synthetic historical figure speaking as if it possesses undocumented memory;
- depicting disputed events as settled without the dispute;
- generating sensitive operational details from inference;
- using a veteran's testimony outside release terms;
- turning suffering or death into decorative spectacle; or
- hiding AI transformation and Source gaps.

## 8. Service and health boundary

The Realm may connect service history to current official benefits, exposure, or health information when the veteran asks. It must:

- use current official terminology and preserve uncertainty;
- distinguish peer experience, public guidance, clinician advice, and benefits determination;
- never diagnose or promise benefits;
- allow a veteran to keep health inquiry separate from public service identity;
- offer warm human/accredited/professional handoff when needed; and
- treat urgent risk as a human-safety escalation, not a content recommendation.

The source concept's trauma-informed aspiration is retained as a Stance proposal, not evidence of clinical validation.

## 9. Default experience and Realm Lens

### Calm default

The active Realm might be the Battle of 73 Easting Oral History Project. The current Focus is “Record what my crew remembers before the anniversary.” Ki explains that the conversation is private until the veteran previews a separate contribution. It elevates an interview outline, the release/visibility choice, and one relevant existing Source. No member directory, feed, or event dashboard dominates.

### Realm Lens proposal

On request, the Lens may show:

- Realm purpose, containing Association/Program, and unverified external relationships;
- archive coverage, custody, migration exceptions, and source health;
- contribution/release and visibility rules;
- editorial authorities, Actors, and appeal paths;
- contested accounts and Scene versions;
- current benefits/health Source freshness;
- recent publication, correction, disclosure, and migration Records; and
- Compute/Treasury only when materially relevant.

Confidential SADUNA planning and private veteran information do not appear merely because someone holds an administrative Role.

## 10. Prioritized user stories

### P0 — Contribute an oral history with durable control

As a veteran, I want to record what I remember and choose how it may be used so my experience is preserved without surrendering privacy or being rewritten by AI.

Acceptance:

- private draft remains separate from submitted contribution;
- release, attribution, scope, sensitive details, retention, and withdrawal limits are previewed;
- original recording is preserved separately from transcript/interpretation;
- edits and disputes create layers and Records, not silent replacement.

### P0 — Explore history without false certainty

As a veteran, historian, family member, or current trooper, I want to explore a documented event through Sources, place, and testimony so I understand both what is known and what remains contested.

Acceptance:

- five truth layers are distinguishable;
- each material claim can reach an inspectable Source permitted to the Presence;
- contested accounts remain present;
- Scene has an editorial authority, version, and Portal back.

### P0 — Connect service history to trustworthy help

As a veteran, I want to ask privately how my service context relates to current benefits or health information and reach the right human help without making my question part of my public profile.

Acceptance:

- private status and source freshness are clear;
- peer testimony is not presented as medical/benefits determination;
- warm handoff requires consent;
- no diagnosis, eligibility promise, or public cross-link occurs.

### P1 — Migrate the archive without false completeness

As an archive steward, I want a reconciled migration with rights and exception reporting so the community can trust what moved and what did not.

Acceptance:

- every object class has source/destination counts and failure states;
- hashes/custody and transformation are recorded;
- uncertain matches remain quarantined;
- visibility is not broadened by migration.

### P1 — Correct a contested historical representation

As a contributor or historian, I want to challenge an annotation or Scene without deleting the underlying evidence.

Acceptance:

- challenge links to exact claim/version;
- affected representation can be constrained pending review;
- original evidence and dissent are preserved;
- editorial decision and appeal are recorded.

## 11. Readiness assessment

**Current level:** Seed. The use cases and source base are rich, but current Association authority, archive custody/rights, exact counts, entity relationships, confidential SADUNA status, editorial governance, service-provider credentials, and migration evidence are unresolved.

The system is ready for fictional Gate 2B behavior testing of oral-history contribution and contested historical truth. It is not ready for archive migration, public historical claims, benefits execution, medical guidance, or public exposure of confidential entity planning.
