About · public doctrine and build surface
StoneyTECH
AI Architecture Applied — citation-first learning results for bounded, audited, deployable agentic systems.
The problem this notebook studies
AI crossed from tool to actor faster than common boundaries, verification habits, and deployment instincts matured. This notebook studies how public work makes legible enough to trust: name the , constrain the , preserve evidence, and keep the system moving toward instead of vibes.
What this notebook is learning
The moves fast enough for confident frameworks tend to age in months. The frame this site is testing from public sources: each lever — Model, API, , , , , — is a way to swap a unit of for a unit of determinism. The engineering move is to push as much of the work down the stack as possible, into known, repeatable execution. The frame gets tested through one cited essay and one reference build at a time.
The working name is . The site publishes learning results: public sources, rebuild notes, failures, and parts still needing a better citation. The axioms are a study lens, not a claim of invention; each one stays only while the cited backing holds.
How the notebook stays honest
The agentic field changes faster than any opinion deserves to. The verification loop below is the current publishing guardrail; it's a working pipeline, not a credential or originality claim. It should keep evolving as the cited work gets better.
6
Independent reviewers per article
GPT-5.5, Claude Opus 4.7, Gemini 3.1 Pro, Grok 4.20, plus GPT-5.5 with security and architecture-context lenses. Convergence at ≥4 of 6, with verification receipts and build notes kept on file.
23
Cited working axioms
Borrowed from Brooks, Knuth, Beck, Hickey, Hamming, Sculley, OWASP, NIST, and later governance work. Every essay declares which axioms it leaned on and what held. The catalog itself keeps getting refined.
advisory by default
When the bar moves, prior pieces move back to advisory
The verification chain has gone through three architectures so far. Each architecture change re-classifies the prior corpus until every piece runs under the new rules.
in code
The discipline lives in the build
A validator refuses to ship the site if any essay claims a verified status without a matching panel run on file. If the publishing step forgets the discipline, the build does not.
Boundary
Personal credentials, employers, private projects, unpublished systems, and original work stay intentionally absent from this public surface. Useful claims depend on public sources and reference builds with inspectable learning trails.