Capablio

Handbook

Execution and release plan

Run prompts 00–02.

Updated

Phase 0 — Baseline and product truth

Run prompts 00–02.

Deliverables:

  • Repository/stack map
  • Current route and role map
  • Dual wiki with feature index, glossary, route map, role matrix, and traceability
  • Architecture decision list
  • Design-system migration plan
  • Security and encryption decision log
  • Backlog grouped by user value and risk

Exit gate:

  • No unresolved ambiguity about tenant resolution, session model, primary roles, response visibility, or current data ownership.

Phase 1 — Foundations and public credibility

Run prompts 03–06.

Deliverables:

  • Design tokens, components, layout shells, stories/examples, and accessibility baseline
  • Marketing site with truthful product/pricing/security content
  • Documentation portal generated from or synchronized with the external wiki
  • Production-grade sign-in, invite, onboarding, account, and recovery flows

Exit gate:

  • A prospect can understand and evaluate Capablio; an invited user can safely reach the app; the public surfaces and product shell share one design system.

Phase 2 — Role completeness

Run prompts 07–11.

Deliverables:

  • Individual, manager, HR, tenant-admin, and global-admin workspaces
  • Role-specific navigation and dashboards
  • Permission-safe data contracts and audit events
  • Replacement of raw prototype controls and JSON views

Exit gate:

  • Each role can complete its top five jobs without using developer tools or inaccessible hidden routes.

Phase 3 — Core product differentiation

Run prompts 12–15.

Deliverables:

  • Question library and pack governance
  • Program builder with cadence, cooldown, quota, PDP, and coverage simulation
  • Campaign/rater lifecycle
  • Results, analytics, imports, and PDP follow-up

Exit gate:

  • The adaptive feedback promise is operational end to end, and results preserve source, sample, anonymity, and interpretation boundaries.

Phase 4 — Enterprise operations

Run prompts 16–18.

Deliverables:

  • Entitlements, billing, integrations, audit, retention, data governance, support access
  • Accessibility/security/performance hardening
  • Migration tools, demo data, SEO, release notes, operational runbooks

Exit gate:

  • A tenant can be sold, provisioned, configured, operated, supported, upgraded, and offboarded under documented controls.
  1. Internal demo tenant with synthetic data
  2. Design-partner tenant with explicit beta agreement
  3. Limited Team plan release
  4. Enterprise pilot with SSO/SCIM and security review
  5. General availability after support, billing, privacy, and operational gates

Release gates

Product

  • All plan promises map to live entitlements.
  • Every navigation destination has released content or is hidden behind an explicit beta flag.
  • No dead links or placeholder claims.

Security and privacy

  • Tenant-isolation tests pass.
  • Privileged support access is audited.
  • Secrets are not exposed in UI, logs, or client bundles.
  • Retention/deletion behavior is tested.
  • Encryption and recovery docs match implementation.

Accessibility

  • Automated checks pass on representative pages.
  • Manual keyboard and screen-reader checks pass for sign-in, survey, results, program builder, and administration.
  • Charts have accessible alternatives.

Reliability

  • Background jobs are idempotent where required.
  • Notification retries and dead-letter handling are visible.
  • Import and sync jobs have status, error detail, and safe retry.
  • Monitoring, alerts, and runbooks cover critical paths.

Content

  • External wiki, docs, UI labels, marketing, and pricing use the same glossary.
  • Release notes and migration notices are published.
  • No fabricated customers, metrics, or certifications.