Evidence / public-safe record
Show the architecture.
Label the claim.
This ledger separates what can be verified from what would require client permission, confidential records, or a future measurement program. Internal builds and reference architectures are not presented as client success stories.
AI agent architectureReference architecture for bounded tools, durable context, observability, and human escalation.Autonomous Company OSInternal/reference system model for persistent coordination and accountable decisions.Marketplace deploymentQualitative source-to-distribution system brief with no invented sales or volume metrics.Research intelligenceEvidence capture and decision-surface architecture for work where the path is not obvious.Production WorkerThe live Obsidian Media site is the public surface for the existing production deployment.Search publishing systemThe production sitemap index exposes the crawlable architecture; it does not imply rankings.
Evidence standard
What this ledger will never do.
- Turn an internal build into a fake client case study.
- Convert architecture into guaranteed business results.
- Publish client names, testimonials, screenshots, credentials, or metrics without permission and source evidence.
- Call Search Console, backlink, revenue, or conversion data “zero” when the platform has not exposed it.
For a project to become a fuller case study, the record needs context, constraints, architecture, implementation, approval boundaries, testing, failure handling, outcome, lessons, and evidence. If the quantitative outcome is unavailable, the page says so.
Read the AI automation failure-mode framework or use the opportunity calculator.