Repository navigation
Description
Documentation Update Summary
Prepare one unsaved, evidence-backed repository-policy amendment package for lightspeedwp/ThisOneTimeOnAcidCom, limited to five existing files.
Reconcile the constitutional prohibition on suggesting Supabase integration with the conditional preference to assess Netlify Functions, Supabase Auth and private manuscript storage/delivery. Distinguish permission to assess from architecture acceptance, constitutional ratification and implementation authorisation.
Ash authorised preparation of the unsaved proposal on 3 November 2026. This does not authorise repository edits, service connections, implementation or deployment.
The outcome is a reviewable policy proposal supporting bounded implementation-prompt preparation—not whole-site readiness or launch approval.
Linked Stories/Tasks/PRs/Epic
- docs: constitution - Prepare manuscript-access planning amendment #519 remains separate. Preserve its capture-only scope, approved specification, existing description, checklists, relationships and GitHub counterpart docs: constitution - Prepare manuscript-access planning amendment #519.
- Existing architecture ADR preparation provides context, not architecture acceptance.
- Existing repository-guidance and locked-file reconciliation work must be consulted without duplicating unrelated cleanup or treating its findings as approval.
The canonical PRD and its approval history remain separate.
No parent, native dependency, development association or closing association is proposed. Do not reuse another issue’s GitHub counterpart or copy contextual references into closing directives.
Milestones & Timeline
No deadline, milestone, release, cycle or estimate is proposed.
Specification number and destination remain unresolved. Required specification/planning artefacts are prerequisites outside this five-file change boundary, not silently authorised additions.
What documentation is needed?
Prepare exact current/proposed wording, source revisions, rationale and preservation accounting for:
.specify/memory/constitution.md- Propose a narrow assessment exception.
- Preserve the prohibition on importing, modifying or reusing protected Supabase artefacts.
- Separate assessment, architecture acceptance, ratification and implementation.
- Identify required authority, amendment process, version decision and truthful approval history.
AGENTS.md- Reconcile the assessment wording conditionally on constitutional ratification.
- Preserve D6’s recorded approval and alternatives while exposing its constitutional conflict.
- Repair the backend-reference link to the existing
guidelines/backend-integration.md.
CONTRIBUTING.md- Apply corresponding authority clarification and backend-reference repair.
- Preserve unrelated contribution, branch, deployment and protected-file rules.
guidelines/Guidelines.md- Replace only the affected Supabase Non-Usage subsection.
- Preserve protected-artefact and connection safeguards except where an exact, separately approved amendment changes their meaning.
- Do not perform unrelated portfolio, identity, styling or tooling cleanup.
guidelines/backend-integration.md- Distinguish the recorded D6 baseline from the conditional candidate.
- Preserve stack assertions as recorded guidance—not verified active services.
- Leave provider, runtime, API, database, ORM and deployment decisions unresolved.
The candidate does not automatically require Next.js, tRPC, Prisma, a database migration or replacing the existing frontend.
Preserve accepted manuscript-access requirements and separate authentication from optional newsletter consent. This work must not attribute verified-access or private-delivery authority to the earlier capture-only approval.
Why is this documentation important?
The constitution prohibits Supabase proposals, while other repository records describe an approved future backend using Supabase. The requested candidate differs from that recorded stack.
Contributors need explicit authority boundaries rather than silently choosing between contradictory instructions. Permission to assess a candidate must not be presented as permission to adopt, connect or implement it.
This remains Ash’s personal book project. No LightSpeed contributors or portfolio material are introduced.
Acceptance Criteria
- Documentation is clear, accurate, and up-to-date
- Includes code examples/screenshots if applicable
- Documentation is accessible and easy to find
- Changelog entry prepared for PR if user-facing update
- PR uses correct branch prefix (docs/)
- PR description updated with relevant details
- Changelog entry prepared for PR (if applicable)
- Labels/types match org standards
- One consolidated unsaved package provides exact current/proposed wording for the five files, with source revisions and rationale.
- Clarifications, source-backed repairs and proposed policy changes are distinguished; unrelated wording and historical decisions are preserved.
- Assessment permission is explicitly separate from policy ratification, architecture acceptance, connections and implementation.
- Protected Supabase utilities remain unchanged and unimported; credential, private-content and connection safeguards remain explicit.
- The existing capture-only amendment issue and its approved scope remain unchanged.
- D6’s approval evidence and alternatives are preserved; conflicting authority and unresolved architecture choices remain visible.
- Specification, clarification/planning, owner authority, protected-file approval, version and amendment-history requirements are identified without claiming satisfaction.
- The file plan contains exactly five conditional Edit operations; additional files require a separate scope proposal.
- Changelog, branch/reuse, association and metadata conflicts are disclosed.
- The final result states its stage-specific limitations without claiming implementation, acceptance or launch readiness.
Additional Context
Evidence baseline
Repository: develop at 84242de7857e1ec03742e20aaaf1df469f44355f.
Organisation branch guidance and shared documentation PR template: lightspeedwp/.github at 47aee0722033f65d4d9d57429b410b518646b817.
Material findings:
- The constitution takes precedence over conflicting repository guidance.
- Amendments require rationale, a separate Spec Kit issue with clarification/planning, owner approval before implementation and a dated amendment entry.
- Critical safeguard redefinition is classified as MAJOR by the existing rules; the precise version requires confirmation.
- The constitution header says ratified, but its history says owner approval pending. Resolve from evidence; do not fabricate or backdate approval.
- Constitutional-owner identity and the effective protected-file approval mechanism remain unverified.
guidelines/is protected/read-only; this file plan does not grant edit permission.- D6 records an approved future Vercel/Supabase/tRPC/Next.js/Prisma stack. It does not establish implementation or resolve the constitutional conflict.
- The Documentation template’s changelog defaults conflict with retained checklist requirements.
- The repository PR router uses
type:documentation, while the Linear template usestype:docs. Keep these systems separate; no taxonomy export or router change is authorised.
Approval gates
- Exact issue creation preview and subsequent approval.
- Review of the unsaved policy candidate—not constitutional ratification.
- Verified owner authority, specification/clarification/planning and protected-file process.
- Exact amendment scope, version and history approval.
- Fresh-baseline five-file diff and separate repository-application approval.
- Separate architecture decision and bounded implementation authority.
Retained merge, branch-deletion and linked-record checklist wording does not authorise those actions automatically.
Next action: review the policy package and resolve authority, amendment metadata, specification destination and protected-file gates.
Branch instructions
- Repository:
lightspeedwp/ThisOneTimeOnAcidCom. - Implementing record: docs: constitution - Prepare backend policy reconciliation #575 is the standalone five-file policy-reconciliation issue. docs: constitution - Prepare manuscript-access planning amendment #519 remains separate capture-only work and is not this package’s implementation target. No branch, PR association or closing target is authorised by this identification.
- Parent: none proposed.
- Allowed closing targets: none yet. Verify the eventual implementing association and whole-outcome coverage separately.
- Base:
develop, verified at the source revision above; refresh before any authorised operation. - Prefix:
docs/is supported for documentation-only work by inspected repository instructions. - Exact branch: withheld. Existing
docs/spec-003-guidelines-reconcilerequires complete scope/diff/base inspection before any reuse recommendation. - PR template: shared
.github/PULL_REQUEST_TEMPLATE/pr_docs.mdinlightspeedwp/.github, at the organisation revision above. Router configuration does not prove automatic insertion. - Validation: no branch-validation commands were run. Exact naming and validation remain prerequisites before branch creation/use.
- Restrictions: no branches, PRs, edits, merges, deployments or hook bypasses are authorised. Preserve unrelated work and all protected-file gates.
Expected file changes
All operations are conditional future edits, not authorised actions.
| Operation | Existing path | Bounded change | Dependency |
|---|---|---|---|
| Edit | .specify/memory/constitution.md |
Narrow assessment exception; preserved safeguards and truthful history | Owner authority, amendment/version approval |
| Edit | AGENTS.md |
Conditional authority clarification, D6 provenance, backend-link repair | Ratified basis and protected-file permission |
| Edit | CONTRIBUTING.md |
Matching clarification and link repair | Same approval gates |
| Edit | guidelines/Guidelines.md |
Affected Supabase subsection only | Resolve protected/read-only edit authority |
| Edit | guidelines/backend-integration.md |
Recorded-baseline versus conditional-candidate distinction | Same protection and ratification gates |
All five paths were inspected at the repository revision above.
Out of scope: the capture-only issue; Spec 003; .coderabbit.yml; new specification/feature-state files; changelog edits; unrelated guidelines; application code; Supabase utilities/imports; schemas; dependencies; accounts; connections; credentials; provider configuration; hosting; workflows; templates; issue hierarchy/status changes; additional contributors.
Scope-change gate: stop for a revised proposal and approval before adding files, changing operation types or weakening safeguards.
Evidence and handoff packet
- Recipient: Ash, for issue-draft and policy-proposal review.
- Source coverage: live registry/template, destination project and labels; overlapping issues; five repository targets; branch instructions/validator/router; shared branch policy and documentation PR template.
- Confirmed issue fields: TOA Triage, No priority and
type:docsonly. The four inherited template labels were removed after explicit approval. No template defaults were changed. - Unresolved: owner authority, amendment metadata, protected-file mechanism, specification destination, branch reuse, changelog applicability and cross-system label mapping.
- External effects: Ash explicitly approved issue creation with two-way GitHub synchronisation on 3 November 2026. Creation of the synced counterpart, GitHub issue docs: constitution - Prepare backend policy reconciliation #575 in
lightspeedwp/ThisOneTimeOnAcidCom, was verified. The subsequently approved label removals and removal of the unintended native relationship were verified in Linear; their GitHub propagation remains unverified. This approval does not authorise additional counterparts, development/closing associations, taxonomy mapping, integration changes or independent export of Linear-only classifications. - Stopping condition: return the unsaved proposal and unresolved decisions; no onward implementation.
- Approval state: issue creation with GitHub synchronisation was approved and completed. The policy amendment remains an unsaved proposal. Constitutional ratification, repository application, architecture acceptance and implementation remain separate and unauthorised by issue creation. All approval gates above remain applicable; the issue-creation gate records a completed authorisation, not a requirement to repeat unchanged approval.
Definition of Ready (DoR)
- Documentation need is clear and well-defined
- Related docs/issues or files linked
- Acceptance criteria listed
- Estimate added if relevant
- Milestone/release assigned (if applicable)
Definition of Done (DoD)
- Documentation meets org standards and guidelines
- Changelog entry prepared for PR (CHANGELOG.md)
- Documentation reviewed for clarity and accessibility
- Screenshots/code examples included if relevant
- PR uses correct branch prefix (docs/)
- PR uses the correct PR template based on
type:docsPR label or linked issue type or linked issuetype:docslabel - Branch deleted after merge
- Linked issue(s) updated with latest status and closed after merge,
- The related epic should not be closed, instead updated with a comment to reflect the closed issue
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
linear-code commentedon Nov 3, 2026
TOA-444