ASV Labs / Public aperture
Not a repo list.
An operating practice.
ASV Labs is where product ideas become working systems—designed locally, tested against real interfaces, and documented well enough for other people to trust the result.
- Build
- Govern
- Verify
- Disclose
Operating layer / Sanitized
Autonomy is useful only when authority, evidence, cost, and rollback remain legible.
01GovernanceHigh-impact actions remain gated, attributable, and reviewable.
02Agent toolingSpecialists operate against explicit task contracts and acceptance checks.
03Agent browser controlCodex agents use the in-app browser to open, inspect, and test real interfaces. Screenshots support the record; they do not replace behavior.
04Evidence systemsClaims travel with provenance, verification state, and public-safety boundaries.
05Local firstDevelopment begins against owned working copies before public handoff or deployment.
Current systems / Evidence required
What is being built.
- 01
Release intelligence
Kinetik
Evidence-backed release review, risk findings, provenance, and generated release notes.
Public receiptOwned repository + sanitized captures↗ - 02
Learning system
Learn
A free hosted learning surface with a public catalog and account-gated lessons, progress, and code space.
Public receiptLive public product↗ - 03
Product system
Foundry Kit
A public website builder organized around portable source export and clear trust surfaces.
Public receiptLive public product↗ - 04
Cross-platform workflow
Creator Studio
An owned creative-production app under active design and Android QA review.
Public receiptOwned repository + emulator evidence↗ - 05
Governed design intelligence
WDI + ADI
Source-aware design gates, composition constraints, provenance, scoring, and multi-viewport verification.
Public receiptGoverned corpora + verification scripts↗
Responsible disclosure
Show the work.
Protect the people.
The public view focuses on the product, the problem it solves, and evidence that it works. Internal infrastructure, customer information, access details, and licensed materials remain private by design.
When a system is ready to discuss publicly, its claims are paired with something useful to inspect: a repository, an owned capture, a working demo, or an approved source.