docs(sps): add six SPS review docs fitted to repo facts

[drferdi]

Summary

Adds only 6 new SPS review docs, each starting with SPS_REVIEW_REQUIRED and fitted to verified repo facts (README, AGENTS.md, LICENSE, package.json scripts incl. deploy:dry-run, folder structure, existing docs/). Scaffold uploads/scaffold-docs.tgz used as skeleton only; generic claims replaced or removed.

Type: docs
Scope: sps-v1

Changes

• docs/PROJECT_OVERVIEW.md
• docs/DECISIONS/README.md
• docs/OWNERSHIP.md
• docs/OPERATIONS.md
• docs/RELEASES.md
• docs/LICENSING.md (references existing LICENSE)

Diff is exactly 6 added files; no existing file edited; tarball not committed.

Gaffer decisions applied (orchestrator, 2026-10-15)

• Licensing follows the proprietary LICENSE file. LICENSING.md records the ISC mentions in README.md §25 and package.json as a mismatch for the owner to fix (stated as fact).
• Production target is belum dikonfirmasi / not yet confirmed in OPERATIONS.md and RELEASES.md, with Railway (docs/deployment.md) and Vercel (.agents/HANDOFF.md) noted as the two conflicting sources.
• Minimum versions are Node 24 and pnpm 11.21.0 per package.json/contract (PROJECT_OVERVIEW.md updated).

Open items

1. Confirm current public contact address and inbox routing for security, licensing, and pilot inquiries.
2. Confirm where future ADRs live and who approves them (second reviewer?).
3. Confirm per-module maintainers, governance security contact, and escalation channel.
4. Confirm branch/merge rules (reviewers, protected paths, merge vs. squash).
5. Confirm monitoring, alert routing, on-call ownership, backup/restore scope, capacity/cost ownership.
6. Confirm who cuts a version and the tagging convention.
7. Designate the release approver and environment gates/evidence.
8. Confirm third-party license obligations/attribution and any components that must remain private.

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentraverse	Ready	Preview	Oct 15, 2026 10:26am UTC

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-15T10:51:20.701570Z	fe07dd9	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.