Adaptive Experience Architecture
Adaptive Experience = Shared Understanding + Domain Services + Outer Harness.
In Plain English: A chatbot should not guess prices or invent inventory. This architecture pairs conversational AI with real store systems (stock, prices, delivery, payment) and an outer harness of checks so orders stay reliable, private, and honest.
This site is the public knowledge surface. It is not a shop, not a CMS, and not a pitch deck.
- The shop is aea.artof.link — Lily's Florist, including
/floristfor staff in a browser. - The knowledge is this site — architecture.artof.link.
- Routes such as
/nativeor/frameworkon the shop host are not documentation pages. Read the companion and Path B notes here instead.
If this site and the repository docs disagree, docs/02-business-analysis/requirements.md and the ADRs win. This site does not invent requirement IDs.
- Shared Understanding is the session's current, reviewable model of what the customer wants (a live digital notepad).
- Domain Services are authoritative: they validate inventory, prices, delivery slots, and payments.
- The Outer Harness keeps both honest in production — guides, sensors, a loop, memory, permissions, and telemetry.
AI may interpret. Domain services decide. Status words are claims; they need a probe. When the build teaches something, Keep Learning and Apply writes it into the harness before the next loop. External agent-OS learning (autonomy ladder, reversibility approvals, handoff packets, connection≠authority, independent checker) maps onto the six layers in Schema — Agent coordination; terms live in the Glossary. Decision-layer learning (thinking vs deciding; Choice·Score·Gate; rebuild option menus; cost per decision) is in Schema — Decision layer and Glossary. Anthropic Building effective agents learning (Workflow vs Agent; Augmented LLM; five composable workflows; ground truth / measured complexity / ACI) is in Schema — Agentic workflows and Glossary. Holmberg/LangChain harness learning (Model-tier Choice; AutoMode pre-tool Gate; recipe families) extends Schema — Decision layer and Glossary (2026-09-21). Status: Documented until Pages probed — cite as learning, not TypeSafe/Jev, Bot, Anthropic, or LangChain product endorsement; no runtime in the docs MR; CloudAgent held.
The Six Outer Harness Layers
The outer harness wraps around domain services and shared understanding across six layers:
| Layer | Plain-English Job | What It Prevents |
|---|---|---|
| 1. Guides | Clear instructions, role boundaries, and playbooks | Prevents out-of-scope actions before work begins |
| 2. Sensors | Automated test checks and fail-closed availability | Catches errors before customers see them |
| 3. Loop | Interpret → Act → Verify → Remember | Stops sprawling tasks: 1 finding → 1 issue → 1 review |
| 4. Memory | Persistent session context across page reloads | Solves AI amnesia without stuffing raw chat history |
| 5. Permissions | Strict controls over who can touch data, funds, or code | Prevents unauthorized merges and self-approval |
| 6. Observability | Real-time telemetry and proof for every status claim | Eliminates guesswork; unprobed claims stay Unknown |
Research papers (2026-10-18)
Canon harness engineering papers on GitLab main under research/pdf-export/ (not shipped in Pages — PDFs stay on GitLab). Dated 2026-10-18 adds section XVIII-N: a "100 tips for a personal AI agent" post (ideas by u/palo888 on Reddit, repackaged by @humzaakhalid), claims unverified; it adds a rule class and reason to Guide Hygiene (#548), a data-freshness rule to Memory and State (#549), parks a devil's-advocate pass (#550) and sharpens #503, #543 and #545 by comment; umbrella #547. Prior tip 2026-10-11 added section XVIII-M: a model-plus-harness survey (arXiv 2606.20683), a Jev re-share and a five-repo agents list, post claims unverified; it adapts Layer/Cause fields on Findings (#543), a task-property table (#544), a confidence-routing policy for the decision layer (#545) and review of third-party skill packs (#546); umbrella #542. Prior tip 2026-10-07 added section XVIII-L: a "300+ AI agents mapped" post and the awesome-ai-agents list, claims unverified. It adapts an Adoption record for new tools and dependencies (#527) and proposes a passive DAST baseline of our own hosts (#528); AI pentesting is parked; umbrella #529. Undated names are the same canon tip. Prior tips: 2026-10-06 two-model search harness (#524–#526), 2026-09-30 r2 Graph Engineering (#509, #510), first 2026-09-30 file (#502–#505), 2026-09-24 Second Brain OS (#489–#495).
Full research
- HTML (canon) · PDF (canon)
- HTML (2026-10-18) · PDF (2026-10-18)
- Prior: HTML (2026-10-11) · PDF (2026-10-11)
- Prior: HTML (2026-10-07) · PDF (2026-10-07)
- Prior: HTML (2026-10-06) · PDF (2026-10-06)
- Prior: HTML (2026-09-30 r2) · PDF (2026-09-30 r2)
- Prior: HTML (2026-09-30) · PDF (2026-09-30)
- Prior: HTML (2026-09-24) · PDF (2026-09-24)
Visual guide
- HTML (canon) · PDF (canon)
- HTML (2026-10-18) · PDF (2026-10-18)
- Prior: HTML (2026-10-11) · PDF (2026-10-11)
- Prior: HTML (2026-10-07) · PDF (2026-10-07)
- Prior: HTML (2026-10-06) · PDF (2026-10-06)
- Prior: HTML (2026-09-30 r2) · PDF (2026-09-30 r2)
- Prior: HTML (2026-09-30) · PDF (2026-09-30)
- Prior: HTML (2026-09-24) · PDF (2026-09-24)
Status: Documented on this site until a post-merge Pages probe. Documented ≠ Live; CloudAgent held; SBOS/Claude, the /advisor feature, graph databases and the tools picked in the 7 Oct post (screenpipe, Cua, Open Interpreter, Strix) are not Path B dependencies. Links point at GitLab blob URLs; do not treat cts-ai copies as the tip.
Explore the Framework & Case Studies
The live flower shop at aea.artof.link is the reference case study. The pages below explain the architecture in plain English, with formal IDs where behavior is cited.
- Read the Comparison & Visual Guide for the 5-floor building model, 3 eras of AI development, and the honest status ledger.
- Explore the Schema for the architectural blueprint, execution loop, and team roles.
- See the Stack for high-level system architecture, cloud deployment, and the two-hostname split.
- Review the Path B Case Study for customer journey recordings and how the web workspace differs from the phone app.
- Open the Path B runtime map (Archify) — same-origin interactive diagram at
/archify/path-b-runtime.html(source HTML) (Documented aid — not Live). - Open the Decision Layer map (Archify) — same-origin diagram at
/archify/decision-layer.html(source HTML) (Documented aid — not Live). - Browse all Archify diagrams — generated same-origin index at
/archify/, also linked from every page footer (Documented aid — not Live). - See the Mobile Companion App for the thin Android client, Need → Pick → Pay, and the verified ledger.
- Learn about Privacy-Preserving CRM for zero-PII customer intelligence, edge wallets, and 14-day address shredding.
- Read the Journal for curated stories of challenges, solutions, and lessons.
- Check the Glossary for plain-English definitions of terms used across this site.