taodeng/ocp

Fork 0

mirror of https://github.com/dtzp555-max/ocp.git synced 2026-07-21 21:15:09 +00:00

Files

T

1c29f4867f chore(privacy): scrub personal identifiers from public repo (#43 )

Removes all occurrences of maintainer's real name and handle from
tracked files in this PUBLIC repository. Replaces with generic terms
like "project maintainer" / "the maintainer".

Files scrubbed:
- CLAUDE.md (2 instances)
- ALIGNMENT.md (Auditor field)
- docs/adr/0002, 0003, 0004 (Authors/Deciders fields + body text)
- memory/constitution.md (1 instance)
- docs/superpowers/plans/2026-04-10-lan-mode.md (Users/taodeng paths → $HOME)

Also:
- Replaces specific machine hostnames (Taos-Mac-mini, Taos-MacBook-Pro)
  with role-based names (home-mac, travel-macbook) in ADR 0001 (if
  committed; currently untracked).
- Replaces /Users/taodeng/ paths with $HOME/ in old plan doc.

NOTE: git history still contains the personal info. See postmortem
(issue TBD) for whether to rewrite history via git-filter-repo.

Co-authored-by: Tao Deng <dtzp555@gmail.com>
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

2026-04-22 11:01:44 +10:00

2.2 KiB

Raw Blame History

OCP Constitution

Core Principles

I. Spec-First Development

All non-trivial features begin with a specification in specs/ before any code is written. Use /speckit-specify to create the spec, /speckit-plan for the implementation plan, /speckit-tasks to generate the task list, then /speckit-implement to execute.

II. Server Integrity (NON-NEGOTIABLE)

server.mjs, models.json, package.json, and keys.mjs are protected files. No spec-driven workflow may modify them without explicit approval from the project maintainer. If a spec calls for changes to these files, halt and escalate.

III. Test-First

Implementation tasks include tests before code. The /speckit-implement command must follow TDD for any logic touching the proxy or model-routing paths.

IV. Additive by Default

Features should be additive — new endpoints, new model entries, new config flags — not modifications to existing contracts unless the spec explicitly justifies the breaking change and the plan documents a migration path.

V. Cross-Device Compatibility

OCP runs on multiple machines. Specs and plans committed to specs/ serve as the cross-device handoff artifact. Keep specs/NNN/tasks.md updated as the canonical work-state file.

Constraints

Follow CC 开发铁律 v1.3 (Iron Rules) as loaded via /cc-rules in CLAUDE.md.
One PR per reviewable unit (Iron Rule 11 IDR).
Independent review required before merge (Iron Rule 10).
Pre-brainstorm prior-art search required (Iron Rule 12).

Governance

This constitution is subordinate to AGENTS.md for project-specific memory policy and to CC 开发铁律 for development discipline. Amendments require a PR reviewed by the project maintainer.

Version: 1.0.0 | Ratified: 2026-04-21 | Last Amended: 2026-04-21

2.2 KiB Raw Blame History