## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `skill-shared-rule-capture`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/skill-shared-rule-capture/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/skill-shared-rule-capture/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/skill-shared-rule-capture/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/skill-shared-rule-capture/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/skill-shared-rule-capture/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/skill-shared-rule-capture/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## MASTHEAD
- **identity:** `skill-shared-rule-capture` v1 · content_hash `33c854a9798f0f7a…` · thread_head genesis
- **thesis:** FLAGGED — this article's thesis does not reduce to one falsifiable root claim — audit finding, not fudged
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/skill-shared-rule-capture/discourse
- **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key
- **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/skill-shared-rule-capture/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `skill-shared-rule-capture`
- **title:** Skill: Shared Rule Capture
- **url:** https://miscsubjects.com/a/skill-shared-rule-capture
- **register:** standard
- **updated:** 2026-07-22T09:52:14.470Z

## Body

---
name: shared-rule-capture
description: Use when the owner restates a rule, correction, or constraint, or when a governor report shows high owner-restatement counts.
---

# Shared Rule Capture — turn repetition into memory

## Overview
When the owner has to say the same thing more than once, the build has failed to remember. This skill captures repeated owner rules as skill or law candidates so future agents load them automatically.

## When to Use
- The owner says "I already told you...", "always...", "never...", "do X before Y", or repeats a constraint.
- You notice yourself about to restate a rule the owner already stated this session.
- A governor or audit report shows high `owner_restatement` counts.

## Core Pattern

1. **Detect repetition.** Note when a rule-like statement appears from the owner.
2. **Draft a skill candidate.** One rule = one concise `shared-law-<topic>.md` or addition to an existing skill.
3. **Ask for approval.** Surface the candidate to the owner with a one-tap approve/reject.
4. **Commit on approve.** Place it in the correct skill directory and update `AGENTS.md` if project-specific.

## Rules

- Capture the rule in the same turn it is stated or confirmed.
- Task-only or capture-only is a half-failure: capture, then run the task, then verify the rule is loaded next time.
- A skill candidate must be <500 words and include concrete triggers, not abstract philosophy.
- Do not capture one-off corrections that are specific to a single bug. Capture patterns.

## Red Flags

- "I keep having to tell you..."
- "Same problem as last time..."
- "Why did you do X again?"
- Writing a long explanation instead of a skill.

## Verify

After capturing: the next agent session that touches the same topic loads the skill and follows it without the owner restating it.

## Claims (0)


## Voxel graph (0 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/skill-shared-rule-capture/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (0)
- chain valid: yes · head: `genesis`

## Provenance (0 model passes)
- chain valid: yes · head: `genesis`


## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/skill-shared-rule-capture/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/skill-shared-rule-capture/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"skill-shared-rule-capture","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest skill-shared-rule-capture|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim skill-shared-rule-capture|tier|assertion`
- **iMessage ask:** `skill-shared-rule-capture|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `skill-shared-rule-capture`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/skill-shared-rule-capture/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/skill-shared-rule-capture/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*