gemstone-nexus · Phase 6

DOC — Practitioner personal Atlas rules

← Documents

Metadata

iddoc_idtitlecategorysource_pathsummarycontent_hashindexed_at
48DOC-PRACTITIONER-RULESDOC — Practitioner personal Atlas rulesreferenceDevResources/docs/DOC-Practitioner-Rules.mdEach signed-in practitioner can save **personal** fixed-response rules in their Atlas segment (`org_id` + `practitioner_id`). These are consulted **after** product-wide `GemStoneGuardRails` and **before/with** ledger context so freelanced answers do not violate personal preferences.5f7b7f069a4cb1881227aceaafa88904f50873ee2026-07-23 13:57:31

Content

# DOC — Practitioner personal Atlas rules

*Personal segment · signed-in only · distinct from GemStoneGuardRails*

## Purpose

Each signed-in practitioner can save **personal** fixed-response rules in their Atlas segment (`org_id` + `practitioner_id`). These are consulted **after** product-wide `GemStoneGuardRails` and **before/with** ledger context so freelanced answers do not violate personal preferences.

## Phrase: "Make that a rule"

Say (chat or voice): **Make that a rule**

1. Must be **signed in** — otherwise GemStone asks you to sign in and does **not** write.
2. Captures the decision from recent conversation turns (or an inline `when … say …`).
3. Inference-search over **active** personal rules for overlap:
   - **Match** → remind you, show the existing rule(s), ask **keep original** vs **use new** (chat or voice).
   - **Keep original** → no write.
   - **Use new** → insert new **active** rule; mark old **superseded** (retained; never deleted).
   - **No match** → create new active rule.

## Rule history

Say: **show my rule history** (or **rule history** / **my personal rules**)

Superseded rules are excluded from normal match; they appear only in history.

## MCP / HTTP

| Tool / path | Purpose |
| --- | --- |
| `POST /mcp/prac_rules/match` | Match active personal rules |
| `GET\|POST /mcp/prac_rules/list` | List active |
| `GET\|POST /mcp/prac_rules/history` | Active + superseded |
| `POST /mcp/prac_rules/propose` | Propose (overlap → conflict) |
| `POST /mcp/prac_rules/commit` | `keep_original` \| `use_new` |
| `GET /api/v1/practitioner_rules` | List active (API) |

Writes require signed-in tenant identity.

## Injection

1. Sovereign / Gemini chat — short-circuit **after** GuardRails, **before** ledger RAG
2. `gather_context` — personal framing after GuardRails
3. Gemini Live — `prac_rules_*` tools + framing when org/prac known from hello

## Migration

Alembic `0011_practitioner_rules` — additive `practitioner_rules` table + RLS (org isolation).

## Boundary

| | GemStoneGuardRails | Practitioner personal rules | HorizonIQ (later) |
| --- | --- | --- | --- |
| Scope | Product-wide | Personal Atlas only | Org-wide / merge |
| Passcode | Yes (SuperAdmin) | **No** (MVP) | Personal passcode deferred |
| Phrase | `add to GemStoneGuardRails …` | **Make that a rule** | Promote into GuardRails deferred |

See `DOC07-Punchlist.md` and `DOC-GemStoneGuardRails.md`.