miscsubjectsAI governance
Evidence review

Skill: Shared Write Law

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-write-law`
- **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-write-law

### 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-write-law/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-write-law/bundle?format=markdown
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/skill-shared-write-law/prompts
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/skill-shared-write-law/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-write-law description: Use when about to edit any shared file in miscsubjects-pages, .claude/skills, or .agents/skills. Prevents write collisions and overwritten work. ---

Shared Write Law — claim before edit

Overview

Shared files in this build are edited by multiple agents. Editing without a claim causes collisions, overwritten work, and repeated fixes. This skill makes the existing AGENTS.md WRITE LAW automatic.

When to Use

  • Before editing any file under miscsubjects-pages/, ~/.claude/skills/, or ~/.agents/skills/.
  • When resuming work on a file you edited earlier in the same session.
  • When you see FILE_CLAIM DENIED or the file is already claimed.

Core Pattern

code
Read file → FILE_CLAIM claim → Edit → FILE_CLAIM release
  1. Read the file first. Never edit a file you have not read this session.
  2. Claim it with FILE_CLAIM claim, passing the absolute path, agent holder, and 90-minute TTL.
  3. Only if the response starts with CLAIMED: — edit the file.
  4. Release when done with FILE_CLAIM release.

Rules

  • DENIED means stop. Read the file fresh, find who holds the claim, coordinate. Do not edit.
  • Claims are per-file. Editing five files requires five claims.
  • Release after your last edit in the session. Do not hold claims you are not actively using.
  • TTL is 90 minutes. If your session crashes, the claim expires automatically.
  • Success prefix matters. A FILE_CLAIM result starting with CLAIMED: succeeded. Parse that prefix, not substring matches on the word "error" elsewhere in the response.

Red Flags — STOP and Claim

  • "I'll just patch this quickly."
  • "The file is probably free."
  • "I'll check the claim after editing."
  • Reading a file and immediately reaching for Edit/Write without FILE_CLAIM.

All of these cause the collisions the owner is tired of fixing.

Common Mistakes

  1. Editing before claiming → Claim first. If denied, do not proceed.
  2. Releasing with wrong holder string → Use the same agent:session-prefix you claimed with.
  3. Assuming free because FILE_CLAIM check said FREE → Claim anyway; FREE can change between check and edit.
  4. Editing a file another agent changed since your read → Re-read, re-claim, merge changes.

Verify

Before every edit, confirm: Read ✓ → FILE_CLAIM claim returned CLAIMED: ✓ → Edit ✓ → FILE_CLAIM release ✓.

Related articles

skill-shared-write-law · condition map

Open evidence map →
Skill: Shared Rule Captureshared topicskill-shared-rule-captureWriting register — prompts, audits, handoffs, owner-facing answersshared topicskill-writing-registerBuild decision matrix — autonomous operating logicshared topicskill-build-decision-matrix
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 Write Law — and what would you need me to tell you first?
ask skill-shared-write-law condition gaps · paste includes §SELF
What good and bad outcomes are documented for Skill: Shared Write Law (studies vs anecdotes)?
ask skill-shared-write-law 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