obsidian-plugin/lllin000_PaperForge
1
0
Fork 0
mirror of https://github.com/lllin000/PaperForge.git synced 2026-07-22 06:50:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

project: move PM rules to .omp/AGENTS.md (omp native context)

Browse source 
- .omp/AGENTS.md created with authoritative project record management prompt
  (auto-loaded by omp into every session context)
- PROJECT-MANAGEMENT.md §7.1 simplified to point at .omp/AGENTS.md
- Deleted project/PROJECT-MANAGEMENT-PROMPT.md (wrong location)
This commit is contained in:
Research Assistant 2026-06-28 22:35:37 +08:00
parent 7b0bb41a9c
commit a6474f1588
2 changed files with 39 additions and 39 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
.omp/AGENTS.md Normal file
View file

@ -0,0 +1,34 @@
# PaperForge — Project Record Management
Project state is split across three layers with distinct roles:
- **Narrative ledger** (`PROJECT-MANAGEMENT.md`) — full history, updated every session end
- **Active queue** (`project/current/ocr-v2-active-queue.md`) — next-work priorities, updated at milestones
- **Archive** (`project/archive/`) — superseded files from `current/`, moved not deleted
## Update Rules
### PROJECT-MANAGEMENT.md — Every Session End
Update before final commit. Touches:
- Executive summary (§0) — one-line current state + next action
- Current status (§2) — test counts, component state, fix table
- Remaining issues (§3) — resolved out, new ones in
- Active queue checkpoint (§4) — next steps
- Decision log (§6) — one line per decision with rationale
- Session timeline (§8) — compressed one-line record
### project/current/ — Milestones Only
`ocr-v2-active-queue.md` updates after major fix series or priority shifts. Never mid-session.
Other `ocr-v2-*.md` files: update only when architecture or evidence changes.
### project/archive/ — Move, Don't Delete
When a current file no longer reflects active truth: prepend archive header (date + reason + replacement), move to `project/archive/`, remove from `current/`.
## Format Conventions
- **Timeline entry** (§8): `| YYYY-MM-DD | Short title | Key results — what was done, what was found | §N.M |`
- **Decision log** (§6): `| YYYY-MM-DD | Decision title | Rationale — why, not what |`
- **Fix table** (§2.3): `| # | Paper + symptom | Root cause | Fix approach | Commit |`

44
PROJECT-MANAGEMENT.md
View file

@ -233,46 +233,12 @@ _Gate 5 blind audit executed on 2026-06-28: 24YKLTHQ (13p) + 4KCHGV2Z (9p). 5 pi
### 7.1 Project Folder Management
Project state is split across three layers. Each has a specific role:
The authoritative prompt for project record management lives in `.omp/AGENTS.md`.
It is auto-loaded by omp into every session context and defines when and how to
update `PROJECT-MANAGEMENT.md`, `project/current/*`, and `project/archive/`.
| Layer | File(s) | Role | Updated when |
|-------|---------|------|-------------|
| **Narrative ledger** | `PROJECT-MANAGEMENT.md` | Full history: architecture, decisions, status, session log | Every session end |
| **Active queue** | `project/current/ocr-v2-active-queue.md` | Next-work priorities, current focus scope | When priorities change, after major milestones |
| **Architecture notes** | `project/current/ocr-v2-*.md` | Boundary docs, evidence surfaces | Only when the architecture or evidence changes |
| **Archive** | `project/archive/` | Superseded files from `current/` | When a `current/` file no longer reflects active truth |
**Rules:**
1. **PROJECT-MANAGEMENT.md** is updated EVERY session end. It receives:
- Executive summary update (section 0)
- Current status refresh (section 2) — test counts, component state
- Remaining issues changes (section 3) — resolved items removed, new ones added
- Active queue checkpoint (section 4) — next steps reflect current reality
- One-line decision entry in Decision Log (section 6)
- Compressed session entry in Timeline (section 8)
2. **project/current/ocr-v2-active-queue.md** is the authoritative "what to do next" file.
Updated AFTER a major fix series, milestone completion, or when priorities shift.
NEVER updated mid-session. Always cross-references the evidence source.
3. **project/current/*.md** files are read-only references between major milestones.
Move to `project/archive/` when:
- The file explicitly declares itself SUPERSEDED or historical
- A newer file replaces its role
- The analysis/evidence it represents is no longer the active truth
- Keep a copy statement in the archive noting why it was archived
4. **Never update `project/current/` mid-session.** Only at a natural breakpoint
(end of session, fix series complete, milestone done). PROJECT-MANAGEMENT.md
IS the in-session ledger.
5. When archiving a file, prepend a header:
```
> **Archived:** YYYY-MM-DD
> **Reason:** why it no longer represents active truth
> **Replaced by:** path/to/new/file.md
```
TL;DR: PROJECT-MANAGEMENT.md updated every session end. project/current/ updated
at milestones only. project/archive/ gets moved-to (not deleted) when stale.
### 7.2 How to Update PROJECT-MANAGEMENT.md