Outcome and product specification

Translate business conversation into a small, testable ProductSpec before selecting repositories or UI.

Problem boundary

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

What it owns

Buyer and painful job
Workflow steps and actors
Entities, actions and failure states
Acceptance tests and non-goals

What research already found

17 industries, 12 teams, 66 use cases, 72 ideas and 12 atoms are already catalogued
Requirements must remain implementation-independent
One valuable workflow is a better starting unit than an entire industry

Open first-principles questions

What is the minimum ProductSpec?
How should assumptions and confidence be represented?
When should a prototype answer a question instead of more chat?

Inputs

ClientContext
Industry model
Conversation

Outputs

OutcomeSpec
ProductSpec
AcceptanceFixtures

Connected knowledge nodes

P01 · Client intelligence and discovery P03 · Curated capability shelf P09 · Data and state plane P12 · Deterministic composition planner

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.

Artifact	Location	State
First-principles framework	`research/actionmodel-builder-research-2026-08-26/outputs/first-principles-framework.md`	existing
Synthetic pilot specification	`research/actionmodel-builder-research-2026-08-26/phase-3/outputs/synthetic-pilot-specification.md`	existing
AutoSaaS method	`/Users/shaansisodia/SISO_Workspace/SISO_Agency/apps/AutoSaaS/framework/autosaas-method.md`	existing
Future verified agent packet	`research/workstreams/P02-outcome-and-product-specification/runs/<run-id>/`	planned