Actionist Knowledge Graph
P08 · Experience knowledge node

Archetypes, shells and layouts

Reuse application-level workflow skeletons without forcing every product into one five-area dashboard.

Problem boundary

What this subsystem owns and what it must hand to the rest of Actionist.

What it owns

  • Case, portal, CRM, scheduling, finance, support and operations archetypes
  • Navigation and page topology
  • Required component slots
  • Industry variation points
  • Responsive shell behavior

What research already found

  • Ten B2B archetypes have been identified
  • Case/workflow and portal demand are strong while clean template supply is thin
  • Generic admin/dashboard templates are abundant but weakly differentiated
  • The inherited five-area ISSO shell is only a hypothesis

Open first-principles questions

  • Which archetypes cover 80% of the first 17 industries?
  • What is universal shell infrastructure versus archetype-specific UX?
  • Which side-nav variations should clients choose visually?
  • How does the shell absorb donor navigation?

Inputs

  • ProductSpec
  • TasteProfile
  • Component selections
  • Capability surfaces

Outputs

  • ArchetypeTemplate
  • NavigationPlan
  • PageTopology

Scientific research protocol

Every research owner uses the same evidence funnel. No padding is allowed when a denominator is inapplicable or evidence is unavailable.

Prior evidence auditRead the canonical spine, all domain-linked artifacts, the 17-industry catalogue and existing contradictions before searching again.
Commercial 100 → 10Define a denominator, map approximately 100 companies/products, and produce first-party dossiers for the strongest 10.
GitHub 100 → 10Search and dedupe approximately 100 relevant OSS projects, then deeply inspect the strongest 10 at the capability and architecture level.
Local estate joinInspect AutoSaaS, Great Library, SISOCRM, 21st stores and other domain-specific precedents already on the laptop.
Innovation 100 → 10Generate a wide divergent idea register, score it against the problem and retain the 10 strongest falsifiable innovations.
First-principles synthesisDecompose the irreducible problem, challenge inherited assumptions, reconcile contradictions and state the minimum sufficient design.
Contracts and experimentsReturn the proposed contract, dependency edges, unknowns, falsifiers, experiments, stop rules and decisions.
Independent verificationA separate verifier checks counts, links, source claims, overlap, contradictions and unsupported conclusions before promotion.

Evidence and agent outputs

Existing research remains source evidence. New agent packets are written to one owned workstream directory and linked here after verification.

ArtifactLocationState
B2B template shelfresearch/actionmodel-builder-research-2026-08-26/phase-8/lanes/03-b2b-template-shelf/outputs/b2b-template-shelf-report.mdexisting
AutoSaaS source and shell strategy/Users/shaansisodia/SISO_Workspace/SISO_Agency/apps/AutoSaaS/framework/source-graph-template-strategy.mdexisting
Industry atom specificationsresearch/actionmodel-builder-research-2026-08-26/phase-2/outputs/industry-atom-specifications.mdexisting
Future verified agent packetresearch/workstreams/P08-archetypes-shells-and-layouts/runs/<run-id>/planned

Agent-sized objective

Define the first archetype contracts and visual shell variants; start with case/workflow and client portal.

See sprint assignment →