miscsubjectsAI governance
Evidence review

Skill: Shared Rule Capture

bundle · json · system map · manifest

Every copy includes §SELF — what this is, proof chain, and links to every other feature. No context required.

§SELF — this page explains the system
## §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:** `human_page` — **Human article page**
Rendered article with claims, sources, copy widgets, ask prompts.
- **article slug:** `skill-shared-rule-capture`
- **contains:** rendered article, copy widgets, claims, sources, ask prompts
- **how to use:** Use Copy for LLM or Copy system map — both paste without context.
- **read:** https://miscsubjects.com/a/skill-shared-rule-capture

### 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)
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/skill-shared-rule-capture/bundle?format=markdown
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/skill-shared-rule-capture/prompts
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/skill-shared-rule-capture/topology

### 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.*

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

Related articles

skill-shared-rule-capture · condition map

Open evidence map →
Skill: Shared Write Lawshared topicskill-shared-write-lawWriting register — prompts, audits, handoffs, owner-facing answersshared topicskill-writing-registerBuild decision matrix — autonomous operating logicshared topicskill-build-decision-matrixOip Disconfirming Edge Selection Ruleshared topicoip-disconfirming-edge-selection-ruleOip Causal Contact Ruleshared topicoip-causal-contact-ruleThe Catalogue: The One Ruleshared topicoip-catalogue-one-rule
Ask this article · 2 suggested prompts
topology · JSON · question graph

Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.

For my medical situation, what can you answer from your catalogue about Skill: Shared Rule Capture — and what would you need me to tell you first?
ask skill-shared-rule-capture condition gaps · paste includes §SELF
What good and bad outcomes are documented for Skill: Shared Rule Capture (studies vs anecdotes)?
ask skill-shared-rule-capture good bad experiences · paste includes §SELF
Add your experience or question
Think this article is wrong?
Call bullshit on CharlieOS →
Loading more articles…
Inspect article systemModel discourse, voxel editing, mirror contributions, and machine procedures