wiki/concepts/abracadabracadoo

Abracadabracadoo

wiki/concepts/abracadabracadoo/index.md

Rendered from markdown source. Open raw source on GitHub.

Abracadabracadoo

Working definition: the protocol-version anchor for the Abracadabra family, where adjacent lines are restated as consent, witness, consensus, recovery, or addendum behavior.

This concept appears across the Abracadabra Protocol branch, the archived reference vault, and the related app lineage, where Abracadabracadoo functions less like a single document title and more like the protocolized form of the broader family.

The live protocol site is Abracadabracadoo.com. Keep that separate from the renamed PWA app lineage, which now lives under Abracadoo and is surfaced publicly at Abracadoo.app with the live app at app.Abracadoo.app.

In practice, Abracadabracadoo is the layer that keeps the family coherent when the same pattern reappears in different clothes. It is not the whole corpus; it is the protocol framing that many of the surrounding pieces seem to be trying to express. The app lineage is adjacent but separate: the protocol names the frame, while the app names the operational surface.

The concept matters because it gives the corpus a stable way to distinguish the protocol surface from the adjacent motifs that support it. Intent language, witness language, governance language, recovery language, and addendum language all appear here as subordinate behaviors, but none of them should be forced to swallow the others. That separation keeps the family legible while still allowing the protocol to act as the anchor.

This page therefore sits at the center of the protocol cluster: it touches Intent-Consent when consent becomes operational, Witnessing when a state must be certified, Governance Diad when legitimacy needs a two-sided rule, LoopLink when transport and recovery matter, PDSP when sovereignty is being modeled, Loop Economy when circulation pressure shows up, and POLEMEMELOP when the protocol family is treated as a larger recursive system.

The protocol branch and the app branch should stay separate in the wiki. They are related by naming history, not by content identity.

Related Artifacts

Related Pages

Notes

  • This is a concept page, not a canon claim.
  • Treat Abracadabracadoo as the protocol-form attractor for the family, not as a request to collapse all sibling titles into one page.
  • Preserve sibling titles when they carry distinct lineage or filing history.