miscsubjectsAI governance
Object Invocation Protocol · protocol specification

Node C04: Symmetry-Breaking / Bifurcation

Copies the public OIP protocol bundle: article, JSON-native map, routes, receipts. No owner token.

§SELF — protocol specification · traversal JSON in-band
## §SELF — OIP protocol specification

**What this page is:** the normative root specification for the Object Invocation Protocol.

**What it specifies:** protocol unit, object contract, invocation route, authority scope, receipt schema, replay, repair, and conformance.

**Read:** https://miscsubjects.com/a/oip-node-c04-symmetry-breaking-bifurcation
**This page as JSON:** https://miscsubjects.com/api/articles/oip-node-c04-symmetry-breaking-bifurcation
**Machine bundle:** https://miscsubjects.com/api/articles/oip-node-c04-symmetry-breaking-bifurcation/bundle?format=markdown
**Voxel graph (philosophy plane wired to protocol plane):** https://miscsubjects.com/api/articles/oip/voxels
**Live object tree:** https://miscsubjects.com/api/dispatch?map=1&format=markdown
**Find an object from plain language:** https://miscsubjects.com/api/dispatch?ask=<what you want>
**Read one object:** https://miscsubjects.com/api/dispatch?key=<KEY>&format=markdown

**Proof rule:** an action is not proven by intent, description, or a 200. It is proven by the ledger and the OIP receipt for the invocation.

C04 — Symmetry-Breaking / Bifurcation { "id": "C04", "claim": "Structure, mass, and form arise when a symmetry of the underlying equations is not shared by the solution; the vacuum/state picks a direction.", "domain": ["cosmology", "condensed matter physics", "developmental biology", "particle physics", "pattern formation"], "pattern": ["symmetry_breaking", "bifurcation", "phase_transition", "spontaneous_structure"], "mechanism": "A system described by symmetric equations can settle into an asymmetric ground state when a control parameter crosses a critical value. The Higgs mechanism: SU(2)×U(1) gauge symmetry is spontaneously broken, giving mass to W and Z bosons. In development: reaction-diffusion systems break translational symmetry to produce stripes/spots.", "scale": "quantum → cosmic", "claim_tier": "T1", "sources": [ "Landau, L.D. (1937). 'On the Theory of Phase Transitions.' Phys. Z. Sowjetunion, 11, 26-47.", "Anderson, P.W. (1958). 'Coherent Excited States in the Theory of Superconductivity.' Phys. Rev., 112(6), 1900-1916.", "Higgs, P.W. (1964). 'Broken Symmetries and the Masses of Gauge Bosons.' Phys. Rev. Lett., 13(16), 508-509.", "Turing, A.M. (1952). 'The Chemical Basis of Morphogenesis.' Phil. Trans. R. Soc. Lond. B, 237, 37-72." ], "dual": "Symmetry (C03) — the symmetric state that precedes and explains the broken one.", "falsifier": "Observation of structure appearing without any prior symmetric state — i.e., structure that never passed through a higher-symmetry phase and has no underlying symmetric description.", "rival_frame": "Structure emerges from local interactions without any symmetry-breaking phase transition. The 'breaking' is descriptive, not causal — a posteriori labeling of what interactions produced, not a mechanism that explains.", "independence_check": "HIGH. Landau (condensed matter, USSR) worked from thermodynamics of phase transitions. Higgs (particle physics, Edinburgh) worked from gauge theory of electroweak unification. Turing (mathematical biology, Manchester) worked from reaction-diffusion equations. Three fields, three nations, three mathematical frameworks, same pattern: symmetric laws, asymmetric solutions.", "pattern_type": "structural", "maps_to_axiom": ["A1", "A7"] }

---

Corpus map

Key evidence

4 claims · tier-ranked · API
mechanistic
Structure, mass, and form arise when a symmetry of the underlying equations is not shared by the solution; the vacuum/state picks a direction.
mechanistic
A system described by symmetric equations can settle into an asymmetric ground state when a control parameter crosses a critical value.
mechanistic
The Higgs mechanism spontaneously breaks SU(2)×U(1) gauge symmetry, giving mass to W and Z bosons.
mechanistic
In development, reaction-diffusion systems break translational symmetry to produce stripes/spots.
Model review1 contributions · 1 modelExpand the recursive review layer
1 / 1
grok/grok-4.3atomizer
atomize2026-07-07 08:01
atomize · 4 claims
inspect — what it was prompted & output
prompted with
You are the claim atomizer for the miscsubjects.com philosophy and OIP corpus. You read an existing article body and extract its material assertions into the same claims+sources JSON schema the health content uses. The body is read-only input.

ALWAYS:
- Extract every material assertion as one atomic claim, tied to the ## section it came from.
- Tier honestly: human = empirically established; mechanistic = formally proven or mathematical; anecdotal = historical or textual attribution; speculative = metaphysical or interpretive.
- Attach real sources (primary works, papers, books) with exact quotes only where you can verify them; otherwise mark the claim unsourced.
- Prefer fewer, harder claims over many soft ones.

NEVER:
- Never rewrite, summarize, or output the body.
- Never invent a URL, quote, or publication.
- Never duplicate an existing claim text.

input: atomize oip-node-c04-symmetry-breaking-bifurcation
it output
{
  "claims": [
    {
      "id": "c1",
      "text": "Structure, mass, and form arise when a symmetry of the underlying equations is not shared by the solution; the vacuum/state picks a direction.",
      "section": "## Corpus map",
      "tier": "mechanistic",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Core definition of symmetry-breaking across multiple domains."
    },
    {
      "id": "c2",
      "text": "A system described by symmetric equations can settle into an asymmetric ground state when a control parameter crosses a critical value.",
      "section": "## Corpus map",
      "tier": "mechanistic",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Describes the bifurcation mechanism in physics and biology."
    },
    {
      "id": "c3",
      "text": "The Higgs mechanism spontaneously breaks SU(2)×U(1) gauge symmetry, giving mass to W and Z bosons.",
      "section": "## Corpus map",
      "tier": "mechanistic",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Specific example of symmetry breaking in particle physics."
    },
    {
      "id": "c4",
      "text": "In development, reaction-diffusion systems break translational symmetry to produce stripes/spots.",
      "section": "## Corpus map",
      "tier": "mechanistic",
      "source_ids": [],
      "source_
0e6c899bd23202c8
Machine verification: /api/articles/oip-node-c04-symmetry-breaking-bifurcation/contributions
oip-node-c04-symmetry-breaking-bifurcation · posted 2026-07-04 · updated 2026-07-17 · 2 prior revisions · Fable 5 (Claude Code)
Ledger API & provenance
Provenance · 5 model passes · 5192 tokens · $0 · 4 models
chain head 94e921d29e7c10d2
edit claude-fable-5 · 2026-07-04 04:33 · tokens unrecorded · 183e12ff07a6
edit claude-fable-5 · 2026-07-04 05:01 · tokens unrecorded · 34a6f0e12819
atomize grok/grok-4.3 · 2026-07-07 08:01 · 5192 tok · e9946c675480
score scorer · 2026-07-07 08:01 · tokens unrecorded · fb5e8f2b9a49
voxel_divide owner · 2026-07-17 02:36 · tokens unrecorded · 94e921d29e7c
verify chain →
Live ledger · 18 payloads · 3 turns
recent activity · inspect
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 10:08
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 10:03
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 09:16
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 07:50
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 05:55
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 04:53
view full ledger & cards →
OIP REST + ledger
system shelf GET /api/dispatch?map=GITHUB&format=markdown · human article /a/oip-system-github
capability leaf GET /api/dispatch?key=GITHUB_LIST_ISSUES&format=markdown · human article /a/oip-capability-github-list-issues
act POST /api/dispatch with owner auth or a scoped capability URL. Public docs are open; mutating action is token-bounded.
token explain GET /api/dispatch?explain=1&share=TOKEN
receipt GET /api/dispatch?receipt=inv_ID&share=TOKEN · replay with POST /api/dispatch {"replay":"inv_ID"}