Agent-readable audit
Pricing file, website summary test, offer clarity map, and recommended fixes.
AI work memory compiler
OB1 is for serious work that should not vanish when the chat closes. It captures sources, decisions, constraints, failures, and proof objects so the next run starts with operating memory instead of a blank prompt.
Pricing page does not answer overage rules or buyer fit.
Make the checker the hero, not a side widget.
Use product-like proof surfaces, not decorative panels.
Previous site looked like a generated SaaS template.
Files, tabs, transcripts, screenshots, links, tool output.
What should future agents preserve, avoid, verify, or reuse.
Durable Markdown packets with provenance and next-run use.
Public artifact, audit trail, workflow, site, dashboard, or kit.
## Next-run brief
Goal: rebuild the domain surface
Pattern: prove with product UI
Keep:
- source maps
- design constraints
- visual self-critique
- verification screenshots
Avoid:
- generic card grids
- abstract AI claims
- decorative dashboards
Proof object:
pricing.md crash-test lab
The loop
The goal is not to save every chat. The goal is to preserve the few pieces of work that should influence the next task: sources, decisions, constraints, failures, proof, and the shape of a finished artifact.
Proof objects
OB1 is useful only when it produces surfaces that future humans and agents can inspect, reuse, or test.
Instrumentation for the new work surface: how much AI compute is moving through real operator workflows.
Build nowA pricing crash-test lab and machine-readable commercial file for buyer agents.
KitA source-inventory and verification workflow for turning messy files into grounded work.
KitA reusable path from raw ideas and notes into source-backed, voice-consistent public work.
Playbooks
Services
OB1 services are scoped around visible artifacts: files, sites, dashboards, source rooms, and operating notes. The point is to leave behind a workflow the next agent can use.
Pricing file, website summary test, offer clarity map, and recommended fixes.
Turn a messy source folder into a source inventory, draft plan, and verification system.
Define what agents should recall, write back, confirm, reject, and reuse.
Next action
Send a site, folder, pricing page, transcript bundle, or recurring workflow. The first job is to make one piece of work compound.