03 — Information architecture

Command Center — intent entry, recommendations, recent repositories and runs.
Library — search and filter all accessible playbooks.
Repositories — manual and connected repository profiles.
Composer — active drafts and generated previews.
Prompt Lab — authoring, linting, version comparison and evaluations.
Run History — generated tasks and artifacts.
Settings — profile, integrations, storage, retention and administration.

On narrow screens, Command Center, Library, Repositories and History remain first-level. Composer appears contextually when a draft exists. Prompt Lab is separated as an advanced section.

Route map

/
/library
/library/[playbookSlug]
/library/[playbookSlug]/versions/[version]
/collections
/repositories
/repositories/new
/repositories/[repositoryId]
/repositories/[repositoryId]/profile
/repositories/[repositoryId]/snapshots/[snapshotId]
/composer/new
/composer/[draftId]
/runs
/runs/[runId]
/lab
/lab/playbooks/new
/lab/playbooks/[playbookId]
/lab/playbooks/[playbookId]/versions/[version]
/lab/evaluations
/settings/profile
/settings/integrations
/settings/integrations/gitea/[integrationId]
/settings/security
/settings/storage
/settings/audit
/admin/jobs
/admin/health

Command Center hierarchy

Hero task entry

A command-style field asks: “What should Codex do?”

It can search and recommend but must not silently invent an executable prompt. Results display:

best matching playbook;
why it matches;
required missing information;
compatible repositories;
risk and default autonomy.

Operational panels

Continue draft
Recommended for selected repository
Recently generated
Repository findings
Recently updated validated playbooks
Integration health only when action is required

Library information model

Filter groups

Task category
Playbook type: Quick Prompt, Guided Playbook, Run Pack
Work mode: Inspect, Plan, Guided, Execute, Recovery
Autonomy support
Risk tier
Stack
Lifecycle
Quality status
Source: Built-in, Private, Imported

Result card content

title and one-line outcome;
category icon;
playbook type;
risk tier;
supported autonomy range;
top stack tags;
lifecycle/quality badge;
version and update date;
favorite control;
“Compose” primary action.

Do not fill cards with the full prompt. The card exists to make a decision.

Playbook detail hierarchy

Outcome and recommended use
Compose action
Risk, autonomy, type and quality summary
What it does
When to use / when not to use
Inputs and repository requirements
Workflow preview
Guardrails and protected behavior
Validation and done-when contract
Compatibility and limitations
Example rendered output
Version history and evidence

Repository workspace hierarchy

identity and source;
stack summary;
readiness/health findings;
command registry;
protected paths and policies;
latest snapshot evidence;
recommended playbooks;
recent runs;
profile edit and refresh actions.

Health findings are not an unexplained numeric score. Each finding needs severity, evidence, rationale and a corresponding playbook or documentation link.

Composer information architecture

Desktop uses three coordinated regions:

Configuration rail: task inputs, profile, scope, autonomy and policies.
Preview canvas: rendered task with collapsible block outline.
Inspector: linter findings, provenance, compatibility and export readiness.

Mobile uses a step flow with persistent preview and issues tabs.

Recommended steps:

Task
Repository
Scope
Autonomy
Validation
Review and export

Run detail hierarchy

run title and generation timestamp;
exact playbook version and digest;
repository-profile snapshot;
normalized inputs;
rendered prompt;
exported artifacts;
lint result;
user notes and feedback;
provenance and audit metadata.

Historical runs are read-only. “Create variation” starts a new draft referencing the historical run.

4.1 KiB Raw Permalink Blame History