Repository
A source container. It may contain one product, many capabilities, patterns, infrastructure and assumptions.
Editable architecture conversation
Understand every moving part before we build the machine.
This map breaks Actionist into separable systems: visual components, taste learning, curated software capabilities, autonomous repo conversion, client discovery, deterministic assembly, host services, editing, verification and continuous learning.
15moving parts mapped
8,515joined UI identities
500prioritized OSS candidates
118builder product surfaces
17target industry models
The end-to-end loop
The client experiences one conversation. Underneath, several independent systems exchange typed outputs.
01Know clientExisting Actionist context + public business signals
02Discover outcomeConversation becomes a bounded ProductSpec
03Recommend capabilitiesNotion-like notes? Calendar? CRM? Portal?
04Choose experienceArchetype, layout, components and taste profile
05Solve compositionCompatible blocks fitted without model improvisation
06Bind hostData, identity, settings, connectors and runtime
07Normalize designSemantic tokens make independent pieces coherent
08Preview and editClient changes wording, layout, modules and behavior
09Verify and learnShip, observe, rerank assets and improve recipes
Composition is not code generation. The planner selects compatible capabilities and bindings; deterministic tooling installs and joins them; AI writes only the remaining semantic adaptation and glue.
The moving parts
Select a part to inspect what it owns, what research already tells us, what remains unresolved, and what a dedicated agent lane would work on. Notes are stored only in this browser.
Words that must stay distinct
Most architecture confusion came from using “block,” “repo,” “component” and “template” interchangeably.
UI component
A visual/interaction primitive such as a sidebar, hero, footer, table, card, picker or form state.
Capability block
A bounded outcome-bearing function with declared inputs, outputs, state expectations and host requirements.
Packaging profile
How a capability is delivered: service, module, transplant, package, adapter, generated pattern or custom delta.
Archetype
An app-level workflow skeleton such as case management, client portal, CRM, scheduling or finance operations.
Assembly plan
The exact compatible capabilities, bindings, components, routes, data resources and glue required for one app.
Current decisions and live bets
Components ≠ taste
The gallery supplies visual pieces and inspiration. The preference learner discovers the client's design DNA.
Repos ≠ blocks
A repository must be understood and assigned a reuse shape before it enters the reusable shelf.
Postgres ≠ universal interface
Use typed data capabilities; keep Postgres as the default for new transactional state we own.
Solver before model
Compatibility, dependency and authority elimination should be deterministic before AI chooses alternatives.
Hand-curated top 100
A deliberately chosen first shelf may teach us more than another million metadata records.
Case/portal pilot
Demand appears stronger and reusable supply thinner than for generic dashboards, making it a better test.