13 / Additional projectIndependent project · Josh Fuller

AOS.

Before committing,
make the reasoning inspectable.

AOS is the working name for a product-decision workspace. Its source includes opportunity views, decision lenses and a commitment flow, alongside a developing research → score → verdict pipeline.

Kind
Decision support / opportunity evaluation
Platforms
Web · private
Stage
Private prototype · live evaluation unverified
Evidence
Text-led case · no interface capture
01 / Implemented, and not yet verifiedFrom inspected source and documentation

Further along in code than in proof.

The implementation is further along than its verification. This ledger keeps the two apart, so neither is mistaken for the other.

Implemented in source

  • Opportunity, lens and commitment views that organize a thesis, its relevance and the decision to pursue it.
  • An evaluation schema that requires sources for named competitors and tracks the searches performed.
  • A research → score → verdict pipeline, with explicit schema and verdict gates.
  • The request boundary for evaluation.

Not yet verified

  • The discovery interface
  • End-to-end verification
  • A green live evaluation
  • Persistence of live results
  • Production adoption

Not offered: public product access or autonomous build capability.

02 / How a verdict is reachedModel assistance, then explicit rules

Assistance proposes. Rules decide.

Model-assisted research and scoring feed explicit schema and verdict gates. The pipeline is implemented; live results, persistence and the discovery interface remain verification gaps.

  1. 01

    Research

    Model-assisted research runs under a schema that requires sources for any named competitor and records the searches performed.

  2. 02

    Score

    Model-assisted scoring feeds an explicit schema rather than deciding on its own.

  3. 03

    Verdict

    Explicit gates decide. Evidence, rationale and stopping conditions stay with the verdict.

“No evidence found” is a bounded research result, never proof that a market is empty.

One considered decision

An absence of evidence is not an empty market.

The data model makes that distinction explicit. Evidence, rationale and stopping conditions belong with the verdict so a founder can inspect the reasoning before making a commitment.

Where it stands

  • StagePrivate prototype · live evaluation unverified
  • In sourceThe evaluation pipeline and request boundary are implemented in source.
  • IncompleteThe discovery UI and end-to-end verification remain incomplete; a green live evaluation and production adoption are not established.
  • AccessNo public product access or autonomous build capability is offered.
  • NameAOS is a working name.

About the evidence

No verified, sanitized interface capture or supported side-effect-free local demo was found. The existing workspace requires account/database setup, and live evaluation uses an external model. This case describes inspected source and documentation; it shows no simulated product UI or private research.

Let’s make
something useful.

Bring the idea you’ve been turning over. We’ll find a clear place to begin.

Start a project