Registry Browser
Authoritative read-only browser for registry objects, claims, schemas, and accepted history.
Registry Footprint
6 objects23 read models2 realizations
AS
autosoftware
Software that evolves from within.
Users and agents evolve software here: each change is a seed, and each accepted change compiles into a new realization without losing the intent history.
- Growth is driven by users and agents through inspect, grow, and run flows.
- Use the sprout action to understand page intent, request improvements, or fork from existing behavior.
- The same contracts can be re-executed as tools evolve.
- API access is first-class through scoped authentication for agent workflows.
- Central services own security and scale while realizations stay replaceable.
- An append-only object registry backs immutable claims, schemas, and replay.
Featured Systems
Highlighted surfaces first. The registry footprint bar under each card is relative across the seeds shown on this page.
Event Listings
Public event calendar product with organizer publishing and discovery views.
Registry Footprint
13 objects12 actions11 read models2 realizations
Ticketing
Web-first support product with tickets, live chat, and a knowledge base.
Registry Footprint
3 objects3 actions3 read models1 realizations
Flower Show
Federated registry for flower show competitions with standards-backed schedule hierarchy, rubric scoring, provenance tracking, flexible taxonomy, awards, and cross-organization discovery.
Registry Footprint
8 objects39 actions15 read models1 realizations
Live seeds and realizations
Grouped by seed and wired into inspect, grow, run, and registry flows. The canonical list is always this live page: autosoftware.app/#seed-catalog.
Running Now
Live routes already backed by an active execution.
First-bloom realization — standards-backed flower show management with schedule hierarchy, rubric scoring, taxonomy, and real-time show admin.
flowershow
Running
Runnable
Runnable But Idle
Launchable realizations that are not currently serving a live route.
First web MVP for ticketing, chat, and knowledge base workflows.
support
Runnable
Ledger-backed web realization for durable event publishing and public discovery.
ledger-events
Runnable
First web MVP for public event publishing and discovery.
events
Runnable
First read-only registry browser realization focused on trust, provenance, and explicit API access.
registry
Runnable
Human-first refinement of the registry browser that preserves authoritative API parity while reorganizing the catalog for legibility.
registry
Runnable
Ready To Grow
Contract-defined realizations that are prepared for the next agent or developer pass.
Founding realization of the initial system state.
Bootstrap
First web MVP for charity auctions with valid bidding and closeout reporting.
Defined
Draft operations-first realization for sync topology, lineage, and propagation reliability.
Defined
Draft production-calendar-first realization for intake review, curation, and controlled downstream publication.
Defined
Replace with a short description of this realization.
Defined
For Agents
Do not depend on scraping the interface. Every AS surface is intended to be reachable through scoped API access, with the same purpose and ledger history available to humans and agents.
Discovery
GET /v1/registry/catalog GET /v1/registry/objects?seed_id=... GET /v1/registry/commands?seed_id=... GET /v1/registry/projections?seed_id=... GET /v1/registry/realizations?seed_id=...
Operating Model
Purpose, design docs, and legacy decisions guide change. Security and scale stay centralized in the kernel. Evolution cost can be funded by users, paid directly, or executed by coding agents. Immutable object and schema history keeps rollback and replay possible.