# Proposal

## Why

OpenSpec has been initialized without capability specifications, while the README and architecture document still describe several superseded behaviors. Establish an evidence-backed baseline so future changes can state precisely which existing contracts they preserve or modify.

## What Changes

- Introduce initial specifications for existing behavior, using the current source and regression tests as evidence. These are new OpenSpec records, not new product features.
- Record authentication boundaries, asynchronous loading order, role restrictions, persistence, and user interactions as requirements with observable scenarios.
- Plan corrections to README.md and docs/architecture.md, including Calendar, removed AI summaries, SPA navigation, SR loading, Manage Time access, contact identifiers, permissions, and debug storage.
- Keep README.md as the product/development entry point and RELEASE_NOTES.md as release history. Link durable behavior to OpenSpec after the baseline is applied and archived.
- Distinguish verified code behavior, synthetic test coverage, and live-browser verification still required. Do not treat historical requests or old documentation as implemented behavior.

## Capabilities

### New Capabilities

- `session-authentication`: Identity acquisition/reuse, SPA/SR session recovery, credential routing and profile gates.
- `opportunity-exploration`: Saved-search queries, pagination, fiscal Reference, coordinated filters, table sorting and indicators.
- `opportunity-calendar`: Reference-bounded monthly scrolling, daily cards, fiscal labels and current-week positioning.
- `product-workloads`: Product enrichment, workload caching, Booking classification, projections and forecast updates.
- `service-requests`: Progressive CRM SR enrichment, saved-search lookup, customer/internal SR details and creation.
- `workload-actions`: Ownership badges, dependent loading, action metadata and validated creation.
- `manage-time`: Weekly entry viewing/editing, task selection, validation and explicit writes.
- `customer-insights`: Installed Base, consumption plans/trends/details and Rate Card exploration.
- `organization-charts`: Local hierarchy storage, contact lookup/creation and opportunities by contact.
- `extension-shell`: Fusion entry points, bookmarks, keyboard shortcuts, modal interaction and printing.
- `preferences-cache`: Persistent preferences, sorting and cache invalidation boundaries.
- `request-debugging`: Request capture, lazy rendering, history lifetime and sensitive-value visibility.

### Modified Capabilities

None. The existing OpenSpec specification inventory is empty.

## Impact

- Planning artifacts are confined to `openspec/changes/document-project-baseline/`.
- Subsequent application updates README.md and docs/architecture.md; successful archive promotes the reviewed baseline to `openspec/specs/`.
- Source, generated distributions, API contracts, browser permissions, dependencies, storage formats and version 1.1.0 remain unchanged by this documentation effort.
- No release, tag, commit, live Oracle write, new authentication behavior, or OpenSpec schema/configuration customization is included.