# ai.com — prototypes

A no-build static collection of current product directions, research, landing-page concepts, the Quiet Sky design system, and historical prototypes.

## Start here

```bash
python3 -m http.server 8080
# http://localhost:8080/
```

Use HTTP rather than `file://`. The generated landing snapshots, Command Center runtime, icon reference, and several archived prototypes fetch local assets.

## Directory map

```text
/
├── index.html                 Curated site hub
├── platform-explorer/         Shared overview, navigation, and evidence hub
├── ai-harness/                Source-pinned context, memory, prompts, and static audit
├── current/                   Active product directions
│   ├── org-brain/
│   ├── people/
│   ├── pricing/
│   ├── hk-workshop/
│   ├── exec-preread/
│   ├── mobile-shell/
│   └── onboarding/
├── research/                  Cited product-system teardowns
│   └── slack-marketplace/
├── landing/                   Current landing-page concepts
│   ├── quiet-sky/
│   ├── kris-longform/
│   └── kris-condensed/
├── design-system/             Current production-backed Quiet Sky reference
│   ├── README.md              Authority, contents, and the system's own rules
│   ├── index.html             Portal and the three-layer status model
│   ├── foundations.html       Canonical tokens, rendered
│   ├── components.html        Patterns, with specimens and geometry diagrams
│   ├── platforms.html         Web, Mobile, and Electron notes
│   ├── logo.html              Production wordmark and compact icon
│   ├── conformance.html       Conflicts, adoption gaps, and proposals
│   ├── tokens.css             Portable semantic token contract
│   ├── tokens.tailwind.css    Tailwind v4 bridge, a fragment no page links
│   ├── site.css               Document chrome
│   ├── demo.css               Specimen stylesheet, ds- classes
│   ├── theme-init.js          Blocking theme bootstrap
│   ├── theme.js               Header theme toggle
│   └── assets/                Logo assets and the Onest variable font
└── archive/
    ├── index.html             Searchable historical catalog
    ├── assets/                Unassigned legacy assets
    └── projects/              Complete historical project bundles
```

## Current URLs

- `/platform-explorer/` — unified architecture, AI harness and prompt entry point.
- `/platform-explorer/evidence.html` — audit entry points and snapshot comparison.

- `/ai-harness/` — visual context/memory atlas and exact-source prompt explorer.
- `/ai-harness/audit.html` — repository-wide static audit and searchable file ledger.

- `/current/org-brain/` — organizational knowledge concept.
- `/current/people/` — agent-grounded people intelligence.
- `/current/pricing/` — market research, models, simulator, and recommendation.
- `/current/hk-workshop/` — HK co-create workshop kit: proposal, run of show, sessions, templates.
- `/current/exec-preread/` — Exec pre-read deck (Oct 2026), with the PDF at `exec-preread.pdf`. Built in the workspace by `docs-product/exec-preread-2026-10-05/build.py`; copy `index.html`, the PDF and the referenced `assets/` across to update.
- `/current/mobile-shell/` — Mobile shell “Option D, minimal”: the `feat/design-revamp` shell with targeted changes, Current ↔ Proposed toggle. Source of truth is the local-only `frontend/web/docs/prototypes/mobile-shell/revamp.html` in the workspace; copy `revamp.html` (as `index.html`), `revamp.js`, `data.js`, `tokens.css` and `fonts.css` across to update. Fixtures are fictional.
- `/current/onboarding/` — first-run journey “Light Threads”: landing → sign up → connect → your areas → handoff in one WebGL scene, on a mock backend (link with `?fresh` so a returning visitor isn't skipped to the handoff). Source of truth is the workspace's `ai-onboarding-prototype/` (Vite + React + three.js); run `npm run build` there and copy `dist/` across as `current/onboarding/` to update. Fixtures are fictional.
- `/research/slack-marketplace/` — Slack Marketplace system teardown.
- `/landing/quiet-sky/` — “Everyone gets an agent.”
- `/landing/kris-longform/` — long-form “Your company. AI native. Today.”
- `/landing/kris-condensed/` — condensed, motion-led version.
- `/design-system/` — current Quiet Sky system.
- `/design-system/logo.html` — existing production logo and compact-icon reference.
- `/archive/` — all historical work.

This cleanup is an intentional URL reset. No redirects are provided for the old root-level and project paths.

## Archive convention

Each historical project lives as a complete bundle under `archive/projects/<slug>/`. Keep its HTML, scripts, styles, media, documentation, and project-specific tools together so internal relative paths remain stable.

To add archived work:

1. Put the full project bundle under `archive/projects/<slug>/`.
2. Add a card to `archive/index.html`.
3. Use a project-relative asset path instead of a root-relative path where possible.
4. Do not add it to the main hub.

`archive/projects/operating-jobs/` is intentionally marked incomplete: its data file and four companion pages were already absent before this reorganization.

## Landing snapshots

The Kris concepts are generated build output, not source. Their framework and asset URLs are rooted at `/landing/kris-longform` and `/landing/kris-condensed`; serve the repository root when testing them. See `landing/README.md` for regeneration notes.

## Design system

`design-system/` is the current source of truth. It uses three explicit layers: canonical Quiet Sky foundations, verified production-backed patterns, and a separate conformance report for deviations. Web is the primary specification; Mobile and Electron are documented only for the contracts they have adopted.

The portable tokens were reconciled with:

```text
/Users/jeetzandawala/aic-whole/frontend/web/src/app/globals.css
```

Only the current Quiet Sky layer is canonical. Product-specific shadcn overrides, Icing tokens, legacy AIC styles, and compatibility bridges are not copied into the token package; their effects are tracked in `design-system/conformance.html`.

`design-system/tokens.css` is a reference contract, not a build dependency. Only the site hub links it; every prototype under `current/` inlines its own copy of the token block. Changing the token file does not propagate to any prototype.

Rendered examples on the foundations and patterns pages are static specimens hand-built from the tokens by `design-system/demo.css`. Nothing imports a production component, so a specimen is evidence about the tokens and the visual recipe, never about behaviour. Add `?theme=light` to any design-system URL to force the light theme.

The previous migration-era reference, proposed custom icon family, outlined logo exports, and design story are preserved as the **Quiet Sky 2026 proposal** at `archive/projects/quiet-sky-design-system-2026/`. The older system bundled inside `archive/projects/command-center/_ds/` and the combined reference at `archive/projects/quiet-sky-launch/design-system.html` are also historical only.

## Adding current work

- Active product direction: create `current/<slug>/index.html`, then add a card to `index.html`.
- Research: create `research/<slug>/index.html`, then add a card to the Research section on `index.html`.
- Landing concept: create `landing/<slug>/index.html`, keep its assets in the same project directory, then add a card to `index.html`.
- Shared product design-system material: add it under `design-system/`; do not create another top-level design-system directory.

## Hosting

For Cloudflare Pages:

- build command: none;
- output directory: repository root;
- root page: `index.html`.

No deployment configuration or redirects are committed.

## AI Harness snapshot

`ai-harness/` publishes the 18 September 2026 documentation snapshot: seven chapters,
sixteen feature walkthroughs, 511 source entries and a repository-wide static audit.
The web evidence is pinned to `origin/dev-sunbeam`. File accounting is exhaustive over
the recorded trees; semantic/runtime completeness is not certified. See
`ai-harness/AUDIT.md` for scope and `ai-harness/REPO-SNAPSHOT.json` for exact commits.

This is a static deployment bundle. Source discovery/build scripts live in the original
workspace under `docs-product/ai-harness/`; they require access to the six source
repositories and are not run by Cloudflare. `ai-harness/VALIDATION.md` records the
original snapshot's checks, not a fresh audit of September 21 code or deployments.

**Publishing sensitivity:** the HTML and downloadable catalog embed internal repository
source. A private GitHub repository does not make its Cloudflare Pages site private.
Confirm the intended audience and hosting access controls before publishing this bundle.

## Platform Explorer integration

The hub now links one Platform Explorer, not two competing atlases. Existing
`/platform-architecture/` and `/ai-harness/` URLs are retained. Shared navigation
loads only the selected page (no iframe or eagerly loaded mega-catalog).

Architecture component inspectors link to related feature flows and prompt sources;
all sixteen harness walkthroughs link back to an architecture component. Some are
related/grouped components rather than exact equivalents; qualifiers say so.
The original architecture and later harness source manifests are not reconciled or
refreshed. Their commit differences are visible in the evidence hub.

Harness step explanations and memory/governance matrices now use progressive
disclosure. Audit findings and the file ledger are collapsed by default. Exact
source text and downloadable evidence are unchanged; short views do not imply
stronger verification.

After replacing an atlas bundle, run `python3 platform-explorer/build.py` from the
repository root. It applies the shared chrome and minimal presentation idempotently.
`connections.json` is the reviewed cross-link map. Shared assets are scoped to avoid
changing the existing diagram layouts. The static links and disclosures work without
JavaScript; component inspection and ledger filtering still require it.

Local browser check: `node platform-explorer/smoke.cjs` (requires Playwright; set
`PLAYWRIGHT_MODULE` if it is not available in the adjacent source workspace).
The user authorized publication after being informed of the site's public visibility.
The private Git repository does not restrict access to the Cloudflare site.
