wiki/projects/abracadoo/architecture-and-trust

Rendered from markdown source. Open raw source on GitHub.

Architecture and Trust

This seam holds the app-side architecture seed and the plain-language trust note for Abracadoo. The material frames the app as a HumanKey-first PWA with a local-first stance, a secret vault boundary, and relationship state that only appears after a witnessed loop.

Current Shape

• 2 documents.

Representative Files

• Abracadoo V1 Redesign Architecture and Initial Roadmap.docx · archive copy
• The Loop We Owe Each Other.md · archive copy

Working Read

The roadmap says Abracadoo should start as a HumanKey-first app: one-way Acquaintances first, local secret storage behind a vault boundary, and relationship state derived from completed loops rather than asserted by a flag.

The manifesto translates that into public language. Trust should have a path, recognition can be one-way, and machine participation still has to sit inside accountable loops.

Related Links

• Abracadoo
• Brand and Overview
• Implementation and Runtime
• Site Variants
• Abracadabracadoo

Next Actions

1. Keep the architecture seed and public trust note together here.
2. Add future app-side design or policy notes only if they strengthen this seam.