04 / PRODUCT OBJECTS · PUBLIC TASKS

A decision is
one small step.

The source introduces a model for software decisions. The reference keeps that object model separate from its own page navigation and test fixtures.

Four public journeys

DISCOVER

Understand the model

BUILD

Make a typed request

JOIN

Find company context

Read the team page
Open the first-party recruiting destination
Continue in the external application

ENTER

Reach the sign-in boundary

Inspect public sign-in
Validate a local input
Stop at the explicitly labelled local outcome

Data contracts

Object	Fields	Lifecycle	Constraint
Public route	id, origin, pathname, family, title, observedAt	Navigation target → loading source evidence → rendered capture or recorded failure	An alias is recorded separately;121 indexed source routes map to14 families.
Article	title, category, publishedAt, sections, figures, relatedRoutes	Listed → opened → read → related page	Text is original sample copy beyond short quoted headings; full source article stays external.
State	nonempty string or structured context (public API definition authoritative)	Input ready → local fixture evaluates → result	Bound local fixture to available options; do not imply a live model request.
Question	key, primitive, instructions, options/rubric as applicable	Defined → evaluated against state → typed answer	Choice needs alternatives; Score needs an ordered rubric; Noul returns a truth measure.
Decision result	value and confidence/distribution where the primitive defines them	Confident branch → action in application code; uncertain → fallback	0.94 is a fixture, not a model measurement. Never infer authorization from confidence.
Email entry	email string, field validity, local outcome	Empty → invalid → valid → local confirmation	No persistence, request, provider redirect or real email delivery.
Reference contract	id, status, evidence, selectors, geometry, verification	Observed → reconstructed → tested → independently reviewed	A changed source, stylesheet or asset hash invalidates its previous comparison.

Typed decision example

StateTyped questionResult + confidenceApplication branch

{
  "state": "Please restore access before our team meeting.",
  "question": {
    "key": "route_to",
    "primitive": "choice",
    "options": [
      "account support",
      "billing",
      "product feedback"
    ]
  },
  "localResult": {
    "value": "account support",
    "confidence": 0.94
  },
  "applicationBranch": "account support"
}

Ready to copy.

The example explains UI data shape; the public API docs ↗ define the production wire format. The app must separately enforce permissions before taking an action.

Roles and private surfaces

Observed roles are an anonymous public visitor and an unauthenticated console visitor. Public docs describe client usage. No verified evidence exposes an authenticated workspace, its navigation, membership controls, billing, history or private error recovery.

Recovery checked the primary sitemap, the 109-entry docs index, direct console entry and public first-party repository material. The private role remains an explicit exclusion; it does not reduce the public component or route denominators.

Inspect recovery attempts and typed exclusions