Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions .quirk/evidence/power-preserving-defaults-36135a0a2886.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
{
"schema_version": "evidence-receipt.v1",
"receipt_id": "qreceipt.power-preserving-defaults.36135a0a2886",
"repository": "Quirk-Systems/.github",
"status": "verified",
"subject": {
"base_commit": "12ccf8f8b0c0d9077a9fae5ae94920f794752b29",
"commit": "36135a0a2886bdf39e5762287863a8834cb19d74",
"changed_paths": ["docs/governance/WORKING_DEFAULTS.md"]
},
"claims": [{
"claim_id": "qclaim.power-preserving-defaults.36135a0a2886",
"claim_type": "evidence",
"authority_effect": "none",
"statement": "The document preserves the prior source byte prefix and adds the nine approved directions. Only this structural assertion and the returned Git blob were checked. Full repository validation, the exact-range gate, fresh-host behavior, and human benefit were NOT_RUN. No admission, runtime change, or deployment is established.",
"evidence_paths": ["docs/governance/WORKING_DEFAULTS.md"]
}],
"artifacts": [{
"path": "docs/governance/WORKING_DEFAULTS.md",
"state": "present",
"git_blob": "b5e4c14fc47f535ad142b35ccbfc3b45d5f073ca",
"sha256": "sha256:dc36f1e8cf553fd3a192b2e0a7b8cd6b8861d41686d4297e99f0a6679235489a"
}],
"verification": {
"commands": [{
"command": "python3 -c 'from pathlib import Path; import hashlib; b=Path('\"'\"'docs/governance/WORKING_DEFAULTS.md'\"'\"').read_bytes(); p=b.split(b'\"'\"'\\n## Power, people, creativity, and portability\\n'\"'\"')[0]; assert hashlib.sha256(p).hexdigest() == '\"'\"'6af5ed22b44518dec3177bc17d057bdefb2c707605579b02b8188c710e2d7106'\"'\"'; assert all(('\"'\"'### %d. '\"'\"' % i).encode() in b for i in range(1,10)); print('\"'\"'PASS: original source preserved and nine additions present'\"'\"')'",
"result": "pass",
"exit_code": 0
}],
"verified_at": "2026-10-14T23:29:56Z"
},
"authority": {"admission_effect": "none", "authority_ref": null},
"correction": null,
"receipt_sha256": "sha256:06cf8551598f3d18c664ad73804a58346545d027624d0f52ce234d32d8f39d52"
}
46 changes: 46 additions & 0 deletions docs/governance/WORKING_DEFAULTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,3 +56,49 @@ Scheduled reviews retain separate last-attempt and last-successful state, covere
Preserve authorization already provided for relevant reversible work. Do not introduce repeated confirmation for the same scope, and do not expand to unrequested publication, spending, external messaging, protected runtime changes, or canonical promotion.

Use the owning repository's validation and receipt rules. Corrections to these defaults update the source and affected projections, with exact scope and evidence. New systems, tools, skills, plugins, and documents must identify their owner and inherited guidance; they do not each need a new governance system.

## Power, people, creativity, and portability

Applied direction: Bryan's 2026-10-14 approval of the nine top-level changes. These extend the existing defaults, not a new constitution, universal checklist, quality score, or execution grant. Select only the distinctions needed for the present work. Installed originals and historical trials keep their own identities and evidence.

### 1. Useful work before machinery

Begin with a person's intended result. REUSE, COMPOSE, or EXTEND an existing procedure before building another when it serves that result. A new name alone does not justify a skill, service, repository, or required document. Separation needs a distinct responsibility, interface, or failure boundary. Expression, pleasure, surprise, belonging, and learning can justify work; immediate revenue and efficiency are not universal tests. Active machinery must earn its upkeep; dormant creative material need not.

### 2. Shared exchange, varied thinking

Keep identity, source revision, protected choices, uncertainty, and permission boundaries in small shared references. Require only the fields relevant to the exchange. Keep stable technical IDs with expressive names and aliases; plain language must remain usable. Preserve original material alongside interpretations. A lyric, sketch, incident, and research question need not follow the same document sequence. Do not reinterpret an old identifier or replace an original with its summary.

### 3. Bound consequences, not exploration

Match checks to concrete effects. Continue already-authorized reversible work without repeated confirmation. Recheck the affected boundary when resources, audience, spending, permissions, or effects change. Stop only the dependent action when possible; an unavailable publisher need not stop private drafting. Host-enforced permissions remain necessary: instructions and favorable evaluations cannot grant access. A fictional game unlock, score, character role, or simulation success never authorizes real publication, payment, credentials, or delegation.

### 4. Participant agency

Scope preferences and contributions to their actual person, purpose, and audience. Preserve disagreement and the right to decline or leave. Provide understandable inspection, correction, export, preference bypass, and withdrawal paths where personal records are used; propagate withdrawals to derived views. Record credit and permitted reuse. Do not make one person's taste a universal default. Delegate only to the appropriate decision owner, not automatically to the founder. Do not claim these rights are implemented merely because they are documented. Retention and deletion must not preserve personal payloads under an indiscriminate immutable-history rule.

### 5. Factors do not define possibility

Keep hard constraints, contextual preferences, and testable hypotheses separate. Permission is not a weighted quality factor. Allow neither, different purpose, and cannot judge yet; keep deliberate departures from past taste available. Preserve the reason and context of a preference, including choices made to protect a later reveal. Use task-specific comparisons instead of a universal Quirk quality score. Record sensitivity or unresolved trade-offs rather than invent precision. Exploration budgets govern effort, not artistic worth.

### 6. Prove concrete portability

Test a named operation between named execution surfaces at recorded revisions: access, meaning preservation, continuation, return, and permission preservation are separate observations. Format validity is not a completed handoff. An attachment route is distinct from shared-storage synchronization. Keep existing Roundtrip 01 and fresh-reader baselines frozen; a new synthetic route cannot fill their missing evidence. Use existing standards and adapters where they fit without assuming universal host support.

### 7. Authority belongs to the record, not the platform

Identify the governing source and accepted writer or reconciliation rule for each mutable record. Custody, search, dashboards, summaries, and database projections do not acquire semantic authority by storing it. Preserve source identity and base revision through adapters. Surface stale or competing revisions; never silently overwrite newer work. Reuse existing record and proposal stores rather than create a parallel registry. Export must preserve meaning and declare losses; it does not expand the recipient's access.

### 8. Outcomes and burden are separate evidence

Compare a proposed improvement with the ordinary workflow using equivalent inputs and stated limits. Record protected-choice preservation, task completion, correction, review, recovery, and maintenance burden where actually observed. Keep estimates, structural checks, deterministic behavior, fresh-agent behavior, human preference, and authorization distinct. Unknown effort is not zero; a replay is not another independent participant. Do not choose a winner for a human or count an unrun trial as a success. Retire optional active machinery that does not justify its burden without deleting useful source material.

### 9. Recoverable commitments

Choose a useful current path without promising compatibility with everything. Keep exact sources, dependencies, cancellation, safe resume, and a practicable export/manual path. For effectful operations, bind retry identity to the intended authorized operation and reconcile uncertain partial completion before retrying; a timeout does not prove no effect occurred. Demonstrate failure and recovery before making a component a consequential dependency. A rollback does not erase consequences or prove nobody was affected.

### Apply through existing companions

Quirk Plugin Planner uses its existing REUSE/COMPOSE/EXTEND/BUILD/HOLD/DROP decisions and keeps N1/N2 local alternatives as trials until compared. Game Studio reuses an existing game or fixture before selecting another engine; playable fiction and real tool authority stay separate. Superpowers supplies scoped execution and verification, not extra approvals for already-authorized reversible work. Supabase candidate rows and Resource Inbox metadata remain projections, not activation. One shared source and one tested consumer are preferable to copies across every plugin.

For several recommendations, provide stable short selection labels when useful and accept mixed dispositions in one reply. A selection may mean apply, challenge, revise, or park; do not silently convert all selections into adoption. Historical A/C working principles, challengeable B, and parked D retain their recorded scope until explicitly changed.
Loading