wiki/projects/abracadabracadoo

Rendered from markdown source. Open raw source on GitHub.

Abracadabracadoo

This branch collects the protocol family documents for the Abracadabracadoo line. The material is split between the core message protocol and the implementation/extensions layer, so it reads as a small but durable protocol family rather than a pile of isolated drafts.

Current Shape

• 6 live protocol documents.
• 3 nested lineage pages organize the set.

Nested Lineage Pages

• Core Protocol
• Implementation and Extensions
• Site Variants

Representative Files

• Abracadabracadoo Protocol Specification.docx · archive copy
• Abracadabracadoo Message Flow.docx · archive copy
• Abracadabracadoo Development Directive.docx · archive copy
• Abracadabradoo Protocol Addendum III.docx · archive copy
• Abracadabradoo Protocol Addendum IV.docx · archive copy
• Abracadabradoo Protocol Addendum VI.docx · archive copy

Working Read

The core protocol is a nested AEAD proof-release scheme. It binds a proof token to the message ciphertext, allowing a recipient to trigger proof release without exposing plaintext to the server.

The extensions layer expands the family in three directions: witnessable loop structures, loop-local time semantics, and conditional deniability. The development directive turns that protocol family into a reference C++ implementation with local storage, tests, and a pluggable architecture. The site-variants rail now stays separate as public delivery evidence, so the protocol pages can stay formal while the site bundles remain readable as outward-facing packaging.

Related Links

• Abracadoo
• Abracadabracadoo
• Intent-Consent
• Witnessing

Next Actions

1. Keep the protocol family separate from the Abracadoo app line.
2. Treat the modification duplicates as collapsed archive lineage, not as new live protocol material.
3. Add more protocol material only when it changes the structure or extension boundary.