runfoo-org/morethanadiagnosis-hub
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
morethanadiagnosis-hub/openspec/changes
History
Claude 0afa81280e
feat(openspec): propose foundational infrastructure specs 
Add three critical infrastructure proposals for implementation readiness:

1. Data Model v1 (Consolidated Schema)
   - All entities from approved features (User, Profile, Forum, Blog, etc.)
   - Field-level data classification (Public/PII/PHI)
   - Relationships, indexes, and retention policies
   - DSR support and migration strategy
   - Target: openspec/specs/data-model.md

2. Authentication & Authorization System
   - OAuth2/OIDC with PKCE for secure auth
   - RBAC (member, moderator, admin roles)
   - Pseudonym support for privacy
   - MFA (TOTP), password reset, account lockout
   - Audit logging for compliance
   - Target: openspec/specs/architecture.md

3. Design System & Component Library
   - Unified components for Android/iOS/Web parity
   - WCAG 2.2 AA+ accessibility built-in
   - Design tokens (colors, typography, spacing)
   - Theming (light/dark/high contrast)
   - Platform-specific adaptations (RN, Next.js)
   - Target: openspec/specs/architecture.md

These proposals unblock implementation work across all features.

/review areas=backend,security,compliance,accessibility,mobile,web,design
2025-11-18 00:17:49 +00:00
..
2025-11-17-accessibility-baseline docs(openspec): archive baseline proposals after successful merge 2025-11-17 23:35:10 +00:00
2025-11-17-architecture-baseline docs(openspec): archive baseline proposals after successful merge 2025-11-17 23:35:10 +00:00
2025-11-17-authentication-system feat(openspec): propose foundational infrastructure specs 2025-11-18 00:17:49 +00:00
2025-11-17-blog-mvp docs(openspec): archive approved proposals after merge 2025-11-18 00:12:03 +00:00
2025-11-17-data-model-v1 feat(openspec): propose foundational infrastructure specs 2025-11-18 00:17:49 +00:00
2025-11-17-design-system feat(openspec): propose foundational infrastructure specs 2025-11-18 00:17:49 +00:00
2025-11-17-forum-mvp docs(openspec): archive approved proposals after merge 2025-11-18 00:12:03 +00:00
2025-11-17-merch-mvp docs(openspec): archive approved proposals after merge 2025-11-18 00:12:03 +00:00
2025-11-17-mobile-stack-decision docs(openspec): archive approved proposals after merge 2025-11-18 00:12:03 +00:00
2025-11-17-podcast-mvp docs(openspec): archive approved proposals after merge 2025-11-18 00:12:03 +00:00
2025-11-17-privacy-compliance-baseline docs(openspec): archive baseline proposals after successful merge 2025-11-17 23:35:10 +00:00
2025-11-17-profiles-mvp docs(openspec): archive web stack, profiles, and resources proposals 2025-11-18 00:14:35 +00:00
2025-11-17-resources-mvp docs(openspec): archive web stack, profiles, and resources proposals 2025-11-18 00:14:35 +00:00
2025-11-17-tribute-mvp docs(openspec): archive approved proposals after merge 2025-11-18 00:12:03 +00:00
2025-11-17-web-stack-decision docs(openspec): archive web stack, profiles, and resources proposals 2025-11-18 00:14:35 +00:00
2025-11-17-wix-migration-plan docs(openspec): archive baseline proposals after successful merge 2025-11-17 23:35:10 +00:00
README.md chore: OpenSpec scaffold 2025-11-17 22:57:40 +00:00

README.md

Changes

OpenSpec change proposals live here during their lifecycle:

  1. Propose — create yyyy-mm-dd-<short-title>/proposal.md using the template
  2. Review — iterate via comments; track decisions and updates in the same folder
  3. Apply — move normative content into openspec/specs/ via PR; link back
  4. Archive — add ARCHIVED.md with reason and pointers

Naming

  • Folder: YYYY-MM-DD-short-title
  • Primary file: proposal.md

Helpers

  • Use /propose, /review, /apply, /archive slash commands for consistency