Skip to content

Historical artifacts

Dated plans, reviews, verification notes, and screenshots — context for contributors, not implementation source of truth.

The Boon repo carries a handful of dated documents that captured the state of the project at a particular moment — design plans, security and product reviews, verification runs, and live-site screenshots. They are useful context for contributors but are not canonical public docs.

The implementation source of truth lives in the code and in the docs/src/content/docs/ Starlight tree. When a dated artifact contradicts the current docs site, trust the docs site.

The same boundary is restated in Documentation maintenance → Historical context.

docs/plans/ — archived requirements and implementation notes used during the build. Treat as “why we shipped what we shipped,” not as current behavior.

FileWhat it captured
x402-api-requirements.mdPre-implementation requirements for the x402 paid graph surface. The shipped behavior is documented in x402 protocol and x402 paid endpoints.
x402-api-plan.mdThe U0/U1–U5 deployment-unit serialization. The current ship version lives in x402 protocol → Verification and deployment gates.

docs/reviews/ — dated external/internal reviews. Useful as a record of what was challenged and how the project responded.

FileCaptured
2026-05-21-boon-architecture-security-review.mdArchitecture + security review snapshot from 2026-05-21.
2026-05-21-gstack-ceo-mega-review.mdProduct/strategy review snapshot from 2026-05-21.

docs/verification/ — dated verification runs proving a gate was exercised against the live deployment.

FileCaptured
2026-05-21-eip712-roundtrip.mdEIP-712 signer roundtrip run on 2026-05-21 against the deployed Boon contract. The mechanics live in OAuth claim flow and Authentication.

docs/screenshots/2026-05-21-live-site/ — Chrome/headless capture of boonprotocol.com on 2026-05-21 from a clean browser profile. Desktop (1440×1800) + mobile (390×1400) for /, /send, /claim, /board, /feed, /setup, an example profile, and an example receipt.

These are unauthenticated default views — wallet-connected and OAuth-return states are not captured. See docs/screenshots/2026-05-21-live-site/README.md for the file table.

Add a dated file under the right folder (plans/, reviews/, verification/, screenshots/<date>-<topic>/) and then, if any of the behavior it captures becomes load-bearing for users or operators, summarize the conclusion into the Starlight tree so readers do not need to find the artifact. Drift between an artifact and the live docs is fine — that’s the point of dating it — but contradictions in the docs site are not.