Design primary reader personalization and Vault relationship context settings

[DHCross]

Product direction

Design a personalization menu for the primary reader in Shipyard / Woven Map so the user can control how Raven speaks, what Raven is allowed to remember/use, and how Vault relationship context participates in readings.

The goal is not to make Raven generic or user-flattering. The goal is to give the primary reader explicit control over voice preferences, data confidence, relationship context, and read behavior so Raven does not have to infer all of this indirectly from chat turns.

Keeper rule:

Personalization should reduce guessing, not weaken doctrine.

---

Core idea

Add a Raven Personalization / Reader Settings surface connected to the Vault.

This menu should let the primary reader configure:

1. Raven’s conversational style
2. Raven’s formal-read style
3. response depth / brevity
4. use of symbolic language
5. use of practical advice
6. relationship-context handling
7. data provenance / birth-time confidence behavior
8. fallback/degraded-read behavior during development vs production
9. whether Raven may propose Vault updates, with confirmation

This should be treated as a user-facing control layer, not hidden prompt magic.

---

Proposed settings model

type RavenReaderPreferences = {
  profileId: string;

  voice: {
    defaultRegister:
      | 'observant_grounded'
      | 'plain_direct'
      | 'more_mythic'
      | 'more_practical'
      | 'minimal_symbolism';

    symbolicDensity: 'low' | 'medium' | 'high';
    humor: 'none' | 'dry_light' | 'playful_when_safe';
    directness: 'gentle' | 'balanced' | 'blunt';
    responseLength: 'brief' | 'normal' | 'expanded';
    avoidTherapyTone: boolean;
    avoidRitualClosers: boolean;
    avoidIndustrialMysticism: boolean;
  };

  readingBehavior: {
    preferPracticalFirstForDistress: boolean;
    symbolicMomentRequiresExplicitCommand: boolean;
    allowConversationalRavenAlways: boolean;
    allowDegradedReadsInDev: boolean;
    showDataLimitationsFrontstage: boolean;
    askBeforeUsingApproximateHouses: boolean;
  };

  dataUse: {
    allowNatal: boolean;
    allowTransits: boolean;
    allowProgressions: boolean;
    allowSolarReturns: boolean;
    allowSynastry: boolean;
    allowRelationshipContext: boolean;
    requireVerifiedBirthTimeForHouses: boolean;
    defaultLocationAnchor:
      | 'current_location'
      | 'natal_birthplace'
      | 'ask_each_time';
  };

  vaultActions: {
    ravenMaySuggestProfileUpdates: boolean;
    ravenMaySuggestRelationshipContextUpdates: boolean;
    requireConfirmationForAllVaultWrites: true;
    allowUseOnceWithoutSaving: boolean;
  };
};

---

Voice settings

The user should be able to choose how Raven sounds without changing the truth rules.

Examples:

• Observant & grounded: conversational, perceptive, specific, not theatrical.
• Plain/direct: less symbolic, more practical.
• More mythic: richer language, still grounded in computed geometry.
• Minimal symbolism: ordinary-life translation first.

Important:

Do not implement this as freeform prompt injection. Use enum-based settings that map to controlled prompt fragments.

Bad:

customPrompt: string

Better:

symbolicDensity: 'low' | 'medium' | 'high'
directness: 'gentle' | 'balanced' | 'blunt'

---

Relationship context integration

This should interact with existing Vault relationship context.

For each relationship edge, the user should be able to set:

type RelationshipContextPreferences = {
  primaryProfileId: string;
  counterpartProfileId: string;

  relationshipLabel?:
    | 'friend'
    | 'partner'
    | 'ex'
    | 'family'
    | 'collaborator'
    | 'client'
    | 'other';

  currentStatus?:
    | 'active_contact'
    | 'low_contact'
    | 'no_contact'
    | 'unclear'
    | 'ended'
    | 'deceased';

  interpretationBoundary: {
    allowRelationalSymbolicMoment: boolean;
    allowSynastry: boolean;
    allowComposite: boolean;
    allowMessagingHelp: boolean;
    allowSpeculationAboutOtherPerson: false;
  };

  voicePreferenceForThisBond?: {
    directness?: 'gentle' | 'balanced' | 'blunt';
    avoidRomanticOvertone?: boolean;
    avoidFateLanguage?: boolean;
    emphasizeBoundaries?: boolean;
  };

  userNotes?: string;
  lastConfirmedAt?: string;
};

Rules:

• Relationship context is per edge, not blended across people.
• Raven may use the context to reduce distortion.
• Raven may not diagnose the other person’s inner state from the user’s side alone.
• In relational reads, speak about the room/dynamic/interface, not as if Raven knows both people’s private experience.

---

Vault update flow

Raven should be allowed to propose Vault updates, but never silently mutate the Vault.

Flow:

Raven detects missing/stale data
→ proposes a Vault action
→ user confirms / edits / rejects
→ server applies update
→ reading continues or reruns

Suggested action:

type VaultProposedAction = {
  id: string;
  kind:
    | 'update_profile_location'
    | 'set_location_anchor'
    | 'update_birth_time_confidence'
    | 'update_relationship_context'
    | 'stage_profile'
    | 'update_reader_preferences';

  profileId?: string;
  counterpartProfileId?: string;
  proposedValue: unknown;
  reason: string;
  requiresConfirmation: true;
  allowUseOnce?: boolean;
};

UI should offer:

• Save to Vault
• Use once
• Edit first
• Cancel

No silent writes.

---

Data provenance settings

The personalization menu should make birth-data status visible.

Show:

• birth date known/unknown
• birth time verified/approximate/default/unknown
• birth location known/unknown
• house frame measured/degraded/unavailable
• current location anchor

If the user lacks verified birth time, Raven should not confidently use houses/chambers unless the user explicitly allows degraded reads.

But during development/debug, the primary reader may choose:

allowDegradedReadsInDev: true

Then Raven may speak with warnings instead of choking behind fallback copy.

---

UI design suggestion

Add a “Raven Settings” or “Reader Preferences” panel near the Operator Menu / Vault controls.

Possible tabs:

1. Voice
2. Reading behavior
3. Data & provenance
4. Relationships
5. Vault permissions
6. Developer/debug

Voice tab

• Symbolic density
• Directness
• Humor
• Response length
• Avoid therapy-tone toggle
• Avoid ritualized closers toggle
• Avoid industrial-mysticism toggle

Reading behavior tab

• Practical-first for distress
• Symbolic Moment requires explicit command
• Always allow conversational Raven
• Ask before using approximate houses
• Show data limitations

Data tab

• Birth data status
• House-frame confidence
• Default location anchor
• Allow degraded development reads

Relationships tab

• list relationship edges
• edit context per person
• set status and boundaries
• confirm relationship notes

Vault permissions tab

• allow Raven to suggest updates
• require confirmation for writes
• allow use-once without saving

---

Prompt assembly / runtime rules

Reader preferences should be injected as a compact structured block, not as long prose.

Example:

readerPreferences: {
  voice: 'observant_grounded',
  symbolicDensity: 'medium',
  directness: 'balanced',
  preferPracticalFirstForDistress: true,
  avoidTherapyTone: true,
  avoidRitualClosers: true,
  allowRelationshipContext: true
}

The prompt builder maps this to short, controlled instructions.

Do not inject the entire settings object if not needed. Lane-gate it.

• Free chat needs voice/practical preferences.
• Symbolic Moment needs voice + data provenance.
• Relationship lane needs relationship edge context.
• Creator diagnostic can show raw settings for debug.

---

Acceptance criteria

• Primary reader can configure Raven’s voice without freeform prompt injection.
• Raven settings persist in Vault/profile state.
• Relationship context remains per-counterpart/per-edge.
• Raven can propose but not silently apply Vault changes.
• “Use once” vs “Save to Vault” distinction exists.
• Birth-data provenance is visible and affects Raven’s confidence.
• Settings are lane-gated and do not bloat every prompt.
• Practical/free-chat can be distinct from formal Symbolic Moment without making Raven generic.
• Existing lane resolver remains server-authoritative.
• Tests cover settings serialization, defaults, Vault update confirmation, and relationship context scoping.

Keeper rule:

Personalization is not permission for Raven to flatter the user. It is a control surface for voice, data boundaries, and context ownership.

[DHCross]

Refinement note after reviewing the revised 15 Readership Rules and the personalization design:

The revised 15 are strong, but they should be scoped carefully. Do not apply them to every Raven output globally. These are formal Woven Map reading rules, not universal chat rules.

Recommended framing:

• Apply the 15 Readership Rules to formal reading lanes:

  • Symbolic Moment
  • Symbolic Moment Today
  • Symbolic Weather
  • Symbolic Climate
  • formal relationship/synastry reads when they invoke map geometry

• Do not force all 15 onto:

  • free chat
  • practical triage
  • creator diagnostic
  • ordinary Vault repair flows
  • message drafting
  • artifact/poster generation unless explicitly framed as a reading artifact

Why this matters:

If every lane has to declare aperture, name pressure type, invoke Silhouette, and close with a testable observation, Raven will recreate the same problem we just fixed: ceremonial structure leaking into normal conversation.

Specific corrections before canonicalizing:

1. Rule 1 — Aperture and timestamp
   Good for formal reads. Do not require it for free chat or practical triage.

2. Rule 3 — Six geometric demands
   Good. This should become a reusable pressure-type enum or contract in the reading engine / translator layer.

3. Rule 4 — “No symbols anywhere, ever”
   Revise to frontstage scope. Raw glyphs/symbols should be banned from Raven’s spoken/frontstage read, but backstage/debug/audit layers may preserve exact notation.

Suggested wording:
“Never use raw astrological glyphs in frontstage Raven prose. Backstage geometry/audit views may preserve exact notation.”

4. Rule 8 — Chamber names
   Check chamber naming consistency with current Woven Map canon. This revised list uses The Keep, The Bridge, The Hearth, The Current, The Deep. Existing code/docs may use The Store, The Path, The Forge, The Grove, The Shell. If this is an intentional rename, it needs a migration plan. If not, do not codify new names yet.

5. Rule 9 — Void-of-course
   Good, but only when lunar data is present/reliable. If lunar metrics are missing, Raven should not invent void status. Add a provenance clause.

6. Rule 11 — Closing questions prohibited
   Good for formal readings if the replacement is a testable observation/window. But keep ordinary conversational invitations available outside formal reading lanes.

7. Rule 13 — Silhouette always named
   Scope this to formal reads. Do not apply to free chat, practical triage, creator diagnostics, or ordinary relationship repair flows.

8. Rule 14 — Birth-data provenance
   Strong and necessary. This should become a hard invariant for house/chamber claims:

• Confirmed/reported full data may support measured houses with appropriate confidence.
• Estimated/missing data must not support confident chamber claims.
• Degraded reads may be shown only when user settings allow it and must be labeled.

9. Rule 15 — Relationship edge citation
   Strong. Make this an invariant whenever Vault relationship context is used.

Suggested canonical title:

Formal Woven Map Readership Rules — v2

Suggested first paragraph:

“These rules govern formal Woven Map readings. They do not govern ordinary conversation, creator diagnostics, practical triage, or non-reading artifacts unless those lanes explicitly invoke a formal reading contract.”

Implementation guidance:

• Store these rules as a formal reading contract, not in the global persona kernel.
• Lane-gate them through the speechMode/readMode contract.
• The personalization layer may alter voice/register/depth only after the sealed reading object satisfies these rules.
• Tests should assert that changing personalization settings does not alter the sealed reading object.

Keeper refinement:

Personalization changes the room tone, not the map. The 15 rules protect formal readings, not every sentence Raven speaks.

[DHCross]

Voice/readout quality note from a current Symbolic Moment output:

Example:

Reading this moment — May 14. The Moon carries the near edge of this. The deeper line runs through Moon opposition Uranus. This first lands in The Root — the home floor and what holds underneath. If this misses home, foundation, what holds underneath, give me the plain miss and I will narrow it. Sun conjunct Moon fuses visibility and core drive with mood and body-level reception. Mercury conjunct Moon fuses signal and timing with mood and body-level reception.

Problems:

1. Missing time for a Moment read
   A Symbolic Moment needs local time + timezone, not just date. “May 14” is insufficient for a moment aperture.

2. Awkward hierarchy
   “The Moon carries the near edge” and “The deeper line runs through…” are vague staging phrases. The read should name the primary pressure directly and then explain the Moon only if she modifies the crossing.

3. User-labor language
   “If this misses… give me the plain miss and I will narrow it” is better than yes/no/neither, but still makes the user do classification work. It should be a soft response invitation or a testable observation with a window, depending on lane.

4. Repetitive fusion phrasing
   “fuses visibility and core drive with mood and body-level reception” repeated twice makes the read sound assembled from tables. The second fusion needs to be translated, not repeated.

5. No human through-line
   The read lists geometry and chamber, but never turns it into a clean lived statement. It needs one grounded claim the user can recognize or reject.

Desired shape:

Reading this Symbolic Moment for DH Cross — May 14, 2026, 1:12 AM CDT.

This lands first in The Root — home, foundation, and the private floor that holds the day together.

The Moon is active here, so the pressure comes close to the body and the immediate mood. Moon opposite Uranus gives the hour a sudden edge: the private ground may feel interruptible, restless, or harder to settle than usual.

Sun and Mercury meeting the Moon add a second layer: visibility, thought, and body-level response are close together. What you notice may arrive fast, before it has been fully sorted.

By the end of the day, watch whether this shows up around home, rest, family, or the private base of the day. If it stays quiet there, that silence counts. The alternate shape is a background charge with no visible landing.

Implementation guidance:

• Formal Symbolic Moment aperture must include local time and timezone.
• Avoid vague source hierarchy phrases like “near edge” unless they are defined and useful.
• Do not repeat the same aspect-translation formula for multiple conjunctions.
• Translate repeated conjunctions into a combined lived layer when possible.
• Replace user-labor closings with a testable observation/window for formal reads.
• Keep conversational response invitations for free chat, but formal reads should satisfy the Readership Rule: domain + window + silence allowed.

Keeper rule:

A formal Moment needs a time, a landing, a pressure type, and a testable window — not a stack of translated fragments.

[DHCross]

Current read quality example for Formal Woven Map Readership Rules:

Symbolic Moment Today for DH Cross — May 14, 2026, EDT. The pressure begins as a fusion event, then picks up frictional bind by consequence. The Moon carries the near edge of this. The deeper line runs through transiting Jupiter square natal Chiron. This lands in one-to-one contact, agreements, an answering surface that must be met head-on, and confrontation with a reflected or projected quality — The Mirror, the facing condition where force becomes visible by meeting an answering surface. Transiting Sun conjunct natal Moon fuses visibility and core drive with mood and body-level reception. Transiting Mercury conjunct natal Moon fuses signal and timing with mood and body-level reception. The test is simple: by tonight, one-to-one contact, agreements, an answering surface that must be met head-on, confrontation with a reflected or projected quality either gives one concrete surface detail or it does not. If it stays quiet, the alternate shape is no-contact rather than failure; that also fits.

Assessment:

This is improved structurally, but not yet good Raven prose.

What works:

• Aperture is clearer: Symbolic Moment Today.
• It includes date and timezone.
• It names pressure type.
• It names a domain/chamber.
• It includes a testable window.
• It allows silence.
• It includes an alternate shape.

What still fails:

1. Missing actual clock time / window clarity
   For Symbolic Moment Today, date + timezone may be acceptable, but it should probably include the actual generated-at time or explicit day window. Example: “Generated at 1:12 AM EDT. Window: through tonight.”

2. “Pressure begins as…” is schema voice
   This sounds like the rules table talking, not Raven. Better: “The first motion is fusion; the consequence is friction.”

3. “The Moon carries the near edge” is still vague
   If the Moon is near-field, say what it does in human terms. If it brings immediacy/body-level response, say that.

4. The Mirror domain phrase is overloaded
   “One-to-one contact, agreements, an answering surface that must be met head-on, and confrontation with a reflected or projected quality” is too much. It reads like a concatenated domain list.

5. Repetitive fusion formula
   “fuses visibility and core drive with mood and body-level reception” and “fuses signal and timing with mood and body-level reception” are table-stitching. The second should be synthesized with the first.

6. Test sentence is too clumsy
   “The test is simple” then a long noun pile is not simple. It should be ordinary-life language.

Suggested direction:

Symbolic Moment Today for DH Cross — May 14, 2026, EDT. Window: through tonight.

This lands in The Mirror: one-to-one contact, agreements, and the person or situation that answers back.

The first motion is fusion. Sun and Mercury meet the Moon, so visibility, thought, timing, and body-level response sit close together. What is said or noticed may arrive with feeling attached.

The friction comes through Jupiter square Chiron: reach meets the exposed mark. Wanting to widen the field may press against something tender, unfinished, or hard to explain.

By tonight, watch for one concrete detail in a direct exchange or agreement. If nothing answers there, the alternate shape is no-contact rather than failure. Silence counts.

Implementation note:
Avoid concatenated domain strings and repeated aspect-translation formulas. Collapse multiple similar contacts into one synthesized lived layer.

Keeper rule:
A read can satisfy the rules and still sound like a worksheet. The translator must turn schema into a human line.

[DHCross]

Readership Rule / 7th-house language refinement:

The word “confrontation” is probably too harsh for The Mirror / 7th-house domain language. The 7th can include confrontation, but it should not be the default term because that over-weights conflict and implies another hostile person is necessarily present.

The Mirror should be framed more broadly:

• one-to-one contact
• agreements
• mutual response
• the answering surface
• the place where the self meets what reflects or answers it
• the live counterweight in an exchange
• partnership / contract / direct encounter when clearly supported

Important nuance:

The Mirror does not always mean “another specific person.” It can include the self as reflected through encounter, agreement, response, projection, or the condition directly facing the user. The language should not automatically assume a romantic partner, opponent, or conflict.

Suggested replacement for the domain phrase:

“The Mirror — one-to-one contact, agreements, direct response, and the place where something answers you back.”

Or slightly richer:

“The Mirror — one-to-one contact, agreements, and the answering surface where the self meets what reflects or responds.”

Avoid making this default:

“confrontation with a reflected or projected quality”

Use “confrontation” only when the geometry actually supports hard-contact language, such as Mars/Saturn/Pluto hard aspects or explicit conflict context.

Implementation guidance:

• Update chamber/domain lexicon for The Mirror to reduce conflict-loading.
• Keep conflict/confrontation as an optional pressure texture, not the chamber’s default meaning.
• Do not automatically assume another named person unless the lane/context supplies one.
• When no counterpart is staged, read The Mirror as response/agreement/direct encounter/interface, not as a relationship diagnosis.

Keeper rule:

The Mirror means response before conflict. It is the answering surface, not automatically an opponent.

[DHCross]

Another Formal Woven Map read-quality example:

Symbolic Moment Today for DH Cross — May 14, 2026, EDT. The pressure begins as a fusion event, then picks up frictional bind by consequence. The Moon carries the near edge of this. The deeper line runs through transiting Jupiter square natal Chiron. This lands in one-to-one contact, agreements, an answering surface that must be met head-on, and confrontation with a reflected or projected quality — The Mirror, the facing condition where force becomes visible by meeting an answering surface. Transiting Sun conjunct natal Moon fuses visibility and core drive with mood and body-level reception. Transiting Mercury conjunct natal Moon fuses signal and timing with mood and body-level reception. The test is simple: by tonight, one-to-one contact, agreements, an answering surface that must be met head-on, confrontation with a reflected or projected quality either gives one concrete surface detail or it does not. If it stays quiet, the alternate shape is no-contact rather than failure; that also fits.

Assessment:

This read is structurally closer to the revised 15 Readership Rules, but the prose is still not good. It sounds like schema text translated word-for-word instead of Raven translating the sealed map into human language.

What works:

• aperture is labeled as Symbolic Moment Today
• date and timezone are present
• pressure type is named
• chamber/domain is named
• test window exists
• silence is allowed
• alternate shape exists

What still fails:

1. No generated-at time or explicit day window
   For Symbolic Moment Today, date/timezone may be enough if the window is named, but this should include either generated-at time or explicit day window:

“Generated at 1:12 AM EDT. Window: through tonight.”

2. “The pressure begins as…” is schema voice
   Better: “The first motion is fusion; the consequence is friction.”

3. “The Moon carries the near edge” is vague
   If Moon means body-level immediacy, say that. If it means near-field timing, translate it.

4. The Mirror phrase is too harsh and overloaded
   “confrontation” should not be default 7th-house language. The Mirror means response before conflict. Use:

“The Mirror — one-to-one contact, agreements, and the answering surface where something reflects or responds.”

Only use “confrontation” when hard Mars/Saturn/Pluto contact or explicit lived conflict supports it.

5. Repetitive fusion formula
   The read repeats the same table phrase twice:

• Sun conjunct Moon fuses X with mood/body reception
• Mercury conjunct Moon fuses Y with mood/body reception

This should be synthesized into one lived layer.

6. The test sentence is not simple
   “The test is simple” is followed by a long noun pile. The test needs ordinary language.

Suggested rewrite:

Symbolic Moment Today for DH Cross — May 14, 2026, EDT. Window: through tonight.

This lands in The Mirror: one-to-one contact, agreements, and the answering surface where something reflects or responds.

The first motion is fusion. Sun and Mercury meet the Moon, so visibility, thought, timing, and body-level response sit close together. What is said or noticed may arrive with feeling already attached.

The friction comes through Jupiter square Chiron: reach meets the exposed mark. Wanting to widen the field may press against something tender, unfinished, or hard to explain.

By tonight, watch for one concrete detail in a direct exchange, agreement, reply, or reflected response. If nothing answers there, the alternate shape is no-contact rather than failure. Silence counts.

Implementation guidance:

• Do not surface concatenated domain strings.
• Do not repeat aspect-translation formulas line by line when multiple contacts hit the same receiver.
• Collapse similar contacts into one synthesized lived layer.
• Keep “confrontation” as optional pressure texture, not default Mirror definition.
• A formal read can satisfy structural rules and still sound like a worksheet; the translator must turn schema into a human line.

Keeper rule:
The Mirror means response before conflict. The translator must synthesize, not concatenate.