first commit

This commit is contained in:
2026-06-11 03:33:14 +08:00
commit 5f555bf342
599 changed files with 142347 additions and 0 deletions

View File

@@ -0,0 +1,28 @@
# Binding Layer
Repo-local binding metadata remains under:
```text
.claude/project-memory/registry.yaml
.claude/project-memory/<project_id>.md
```
This is the runtime binding layer only.
It may record:
- `project_id`
- `project_slug`
- `repo_roots`
- `vault_root`
- `hub_note`
- `note_language`
- `status`
- `auto_sync`
- recent sync summary
It must not be treated as the project knowledge layer.
The project knowledge layer lives inside:
```text
Research/{project-slug}/
```

View File

@@ -0,0 +1,18 @@
# Daily Promotion Rules
`Daily/` keeps process notes, raw meeting notes, scratch ideas, and temporary observations.
Promote content out of `Daily/` when it becomes:
- a reusable source note
- a durable knowledge note
- an experiment definition
- a stable result
- a writing artifact
Promotion defaults:
- source-centered material -> `Sources/*`
- cross-source synthesis -> `Knowledge/`
- planned or running work -> `Experiments/`
- stable interpreted finding -> `Results/`
- round or batch retrospective -> `Results/Reports/`
- prose deliverable -> `Writing/`

View File

@@ -0,0 +1,46 @@
# Directory Schema
The only default project root is:
```text
Research/{project-slug}/
```
Required files and folders:
```text
00-Hub.md
01-Plan.md
02-Index.md
Sources/
Papers/
Web/
Docs/
Data/
Interviews/
Notes/
Knowledge/
Experiments/
Results/
Reports/
Writing/
Daily/
Maps/
Archive/
_system/
registry.md
schema.md
lint-report.md
```
Defaults:
- `Sources/Papers/` is the only default paper-note directory.
- `Results/Reports/` is the default subdirectory for round or batch experiment reports.
- `Maps/` contains derived artifacts only.
- `Daily/` is preserved by default.
Do not create by default:
- top-level `Papers/`
- `project/KB/`
- project-local JSON or YAML note registries
- `.base` files unless explicitly requested

View File

@@ -0,0 +1,51 @@
# Hub, Plan, and Index
## `00-Hub.md`
Use as the project landing page.
Must contain:
- project summary
- current focus
- current questions
- next actions
- important links
- recent important changes
## `01-Plan.md`
Use for durable plans and active tasks.
Must contain:
- current priorities
- active tasks
- experiment queue
- writing queue when relevant
- current research state when the project has an active research question
Recommended research state block:
```md
## Current Research State
Current question:
Current hypothesis:
Strongest evidence:
Weakest evidence:
Open blockers:
Next experiment:
Do not repeat:
Last decision:
```
Keep this state in `01-Plan.md`. Do not create a separate `.scholar/state.md` for the default Obsidian workflow.
## `02-Index.md`
Use as the human-friendly MOC.
Rules:
- do not mirror the full registry
- list only important and currently active notes
- group links by `Sources`, `Knowledge`, `Experiments`, `Results`, `Writing`, and `Maps`
- keep the note readable as a project directory page

View File

@@ -0,0 +1,19 @@
# Lifecycle Rules
## Project lifecycle
- `detach`: remove or disable repo binding, keep vault project content in place
- `archive`: move the entire project to `Research/_archived/{project-slug}-{date}/` and disable sync
- `purge`: permanently delete binding metadata and the vault project root
## Note lifecycle
- `archive`: move a canonical note into `Research/{project-slug}/Archive/`, repair links, update registry and index
- `rename`: rename or move a canonical note in place, repair links, update registry and index, and do not create archive history
- `purge`: permanently delete a canonical note, repair links, and record the removal in archive history when appropriate
## Defaults
- “remove project knowledge” means `archive`, not `purge`
- note archive history remains visible in `_system/registry.md`
- archived notes may still be referenced for historical context, but they are not active canonical notes

View File

@@ -0,0 +1,15 @@
# Lint Rules
The lint system should check at least:
- missing registry entries
- registry paths that do not exist
- missing index entries
- broken wikilinks
- orphan canonical notes
- duplicate source notes
- experiments without results
- results without experiments
- knowledge notes without sources
- Daily notes with promotable content
- archived notes still referenced by active notes
- canvas nodes that point to missing notes

View File

@@ -0,0 +1,36 @@
# Registry Rules
`_system/registry.md` is the only visible project registry.
## Sections
- Sources
- Knowledge
- Experiments
- Results
- Writing
- Maps
- Archive
## Rules
- Every canonical note must have a registry entry.
- `Daily/` notes are not registered by default.
- Registry entries use stable IDs that do not depend on note titles.
- Archive keeps history; archiving does not delete registry history.
- Paths are rendered as wikilinks.
- The registry is machine-parsed from Markdown tables; do not create a second formal JSON registry.
## ID defaults
- source paper: `paper-001`
- source web: `web-001`
- source doc: `doc-001`
- source data: `data-001`
- source interview: `interview-001`
- source note: `note-001`
- knowledge: `knowledge-001`
- experiment: `exp-001`
- result or report: `result-001`
- writing: `writing-001`
- map: `map-001`