The Harithsa Notes

SDLC guide

Changes are tracked in GitHub and delivered through a protected main branch. Application and documentation deployments have separate verification records.

Intake and sprint planning

Open a bug, feature or task using the issue forms. Add expected behavior, scope and acceptance checks. Use the project views for milestone, sprint, status and roadmap. Give the issue and implementation PR the same milestone when the work is planned.

Develop and review

Create a short-lived branch from main and open an issue-linked PR. State the documentation impact and link the changed guide or explain why the existing guides still apply. Attach check results and concise evidence. Use synthetic fixtures for access and publishing tests.

Foundation and Website are required on main. The solo-maintainer rules require a PR and zero independent approvals. Wait for the checks on the candidate, then merge through GitHub.

Promote changes

Use an isolated Firebase preview when a runtime change needs acceptance tests. Verify the intended revision, access controls, and public reads before promoting it. Documentation changes publish from the default branch through the Pages workflow.

Record the source SHA, workflow or release evidence, and verified URLs. Close the issue after its acceptance checks pass.

Recover a release

For Pages, correct the change or revert it through a PR, then verify the published revision. For the application, use a compatible previous Hosting and Function pair or roll forward. Retest anonymous denial, invited access and publishing with synthetic preview data before promoting the recovery. Preserve memberships, revocations, immutable revisions, media classifications and pending events.

Related links