convez.ai
AgenteProdutividadeAvançado
keith-nielsen

Value Memory Mining

keith-nielsen/2026-AI-Value-Memory-Mining

Pipeline spec-driven de mineração de conhecimento pessoal com template Obsidian

Ver no GitHub
BomPluginScore · de 0 a 100

Sistema de conhecimento pessoal baseado em metodologia de mineração de valor, com vault template forkável para Obsidian e showcase OpenSpec SDD. Organiza captura, refinamento e polimento contínuo de conhecimento através de um pipeline estruturado (Claims → Dig → Ore → Sort → Refine → Treasury).

Instalação

$npx convez-ai keith-nielsen/2026-AI-Value-Memory-Mining

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
0
Acompanhando
0
Saúde
100%
Último commit
há 2 semanas
Versão
v0.1.57
Issues abertas
3
Contribuidores
2

Casos de uso

  • Construir sistema de conhecimento pessoal robusto e metodizado
  • Aplicar prática spec-driven em projetos de ferramentas pessoais
  • Organizar captura e refinamento incremental de informações valiosas

Veredito

Projeto maduro e bem-estruturado que combina metodologia sólida (Value Mining) com governança formal (OpenSpec). Ideal para quem busca rigor documentado em sistemas de conhecimento, mas exige comprometimento com a disciplina e uso de Obsidian.

README

A tradução para o português deste README ainda está na fila.

value-memory-mining

A professional-grade, spec-driven personal knowledge system built on the Value Mining methodology — stake Claims, work Sites, grade the Ore, Refine high-grade material into lasting Bullion, Polish indefinitely.

CI OpenSpec License Obsidian


What Is This?

value-memory-mining is two things at once:

  1. A forkable vault template — copy vault-template/ and you have a production-ready personal knowledge system with working scripts, note templates, Catalog MOCs, a commit-gate hook, and a documented methodology.

  2. An OpenSpec SDD showcase — the repository is itself governed by OpenSpec v1.4.1: a formal project spec, a constitution with constitutional protection, 8 ADRs, 6 capability specs, and a live change-management workflow. It demonstrates what a principled, spec-driven personal-tools project looks like.


The Value Mining Method

Value Mining treats personal knowledge like a mining operation. Material flows through a defined pipeline; only high-grade material reaches the Treasury.

Capture (20-Claims)
  └─► Dig ──► Ore ──► Sort ──► Refine ──► 40-Treasury ──► Polish
                                      │
                              ┌───────┴───────────┐
                         Crucible (rare)    Tailings (slag, retain)
                                                   │
                                             Spoil (terminal)
StageWhat you do
ClaimDrop raw captures into 20-Claims/ without evaluation
DigActive extraction — research, notes, experiments
OreDigging produced something; estimate the grade
Sort3-way triage: Refine / Crucible / Tailings / Spoil
RefineDistill durable value into a Treasury knowledge note
PolishPerpetual upkeep of high-value bullion

Grade = value only, never effort. coal < bronze < silver < gold


Three-Layer Architecture

LayerFolderNature
Layer 0 — Operations99-Operations/Mine machinery; human-write-only; literate meta-scripts
Layer 1 — Treasury40-Treasury/Refined bullion; never deleted by automation
Layer 2 — Workings10-Logbook/, 20-Claims/, 30-Sites/, 70-Tailings/, 71-Spoil/Capture, logs, active/slagged sites

Agents may only write to their assigned Site and _refine-proposals/. Nothing enters 40-Treasury/ without explicit human approval (the deposit-not-merge gate).


System Diagrams

Seven Mermaid diagrams cover the full system — see docs/diagrams.md. Render them in Obsidian or any Mermaid-capable viewer.

#DiagramAnswers
1Value Chain OverviewEnd-to-end material flow
2Effort LifecycleValid states and transitions
3Refine Pipeline (Swimlane)Who does what; where is the gate?
4Sort RouterHow ore gets triaged
5Folder Stack + LayersPhysical structure by layer and touch frequency
6Layer 0 GitOps LoopHow the self-describing Operations layer works
7Containment BoundaryWhat each actor can touch; structurally impossible paths

Repository Layout

2026-AI-Value-Memory-Mining/
├── openspec/                    # OpenSpec SDD (spec-driven project governance)
│   ├── project.md               #   purpose, invariants, standing goals
│   ├── constitution.md          #   constitutional protection + Informed-Upheaval Protocol
│   ├── adr/                     #   8 Architecture Decision Records (ADR-0001–0008)
│   ├── specs/                   #   6 capability specs (vault-structure, value-pipeline, …)
│   └── changes/                 #   change workflow: archive/, live/, templates/
│
├── vault-template/              # Forkable vault skeleton
│   ├── 00-Docs/                 #   onboarding (deletable)
│   ├── 10-Logbook/              #   daily notes + kanban
│   ├── 20-Claims/               #   raw captures + refine pipeline queue/approved
│   ├── 30-Sites/                #   active workings
│   ├── 40-Treasury/Catalog/     #   bullion + 7 Catalog MOCs (6 pillars + Home)
│   ├── 70-Tailings/             #   slagged ore (retained)
│   ├── 71-Spoil/                #   terminal: spent husks + waste
│   ├── 97-Molds/                #   4 note templates (daily, effort, knowledge, moc)
│   ├── 99-Operations/           #   Layer 0: 13 literate meta-scripts + schemas + config
│   └── CLAUDE.md                #   agent conventions for vault operations
│
├── docs/                        # Project documentation
│   ├── diagrams.md              #   7 Mermaid system diagrams
│   ├── glossary.md              #   full Value Mining vocabulary
│   ├── method.md                #   method walkthrough (narrative)
│   ├── obsidian.md              #   recommended Obsidian setup + integration
│   ├── research.md              #   background research summary (2026 landscape)
│   └── USING-THIS-TEMPLATE.md  #   fork quick-start guide
│
├── .github/                     # GitHub integration
│   ├── workflows/ci.yml         #   CI: openspec validate + constitution-lint + naming tests + md-lint
│   ├── ISSUE_TEMPLATE/          #   bug.yml + change-proposal.yml
│   ├── pull_request_template.md
│   ├── CODEOWNERS
│   └── dependabot.yml
│
├── LICENSE                      # Apache-2.0
├── NOTICE                       # Third-party attribution
├── CONTRIBUTING.md              # Change flow + constitution-override path
├── AGENTS.md                    # AI agent access rules + constitutional hard stop
├── CHANGELOG.md
├── CODE_OF_CONDUCT.md
└── SECURITY.md

Constitutional Protection

Thirteen architectural invariants are ordered by criticality band and protected by protects: frontmatter tags on spec files. CI enforces their presence.

BandInvariantsExamples
SubstrateINV-1–3Format (Markdown+YAML), one-commit-per-op, no-auto-fix
SafetyINV-4–8Agent write scope, Layer 0 ownership, no secrets, offline scripts
ValueINV-9–10Treasury immutability, Tailings retention
ConsistencyINV-11–13Naming rules, no pillar folders, wikilinks

Changing a constitutional element requires the 4-gate Informed-Upheaval Protocol (CHECK → PLAN → EXECUTE → RE-CHECK + HUMAN SIGN-OFF). AI agents may draft the first two gates; the sign-off gate is human-only.

See openspec/constitution.md for the full protocol and AGENTS.md for the verbatim AI-agent hard stop.


Fork Quick-Start

# 1. Fork this repo on GitHub, then clone
git clone https://github.com/<your-username>/2026-AI-Value-Memory-Mining.git
cd 2026-AI-Value-Memory-Mining

# 2. Copy the vault template
cp -r vault-template/ ~/Documents/my-vault
cd ~/Documents/my-vault

# 3. Configure your pillars
#    Edit 99-Operations/config.env → PILLARS="..."
#    Update 40-Treasury/Catalog/ MOCs to match

# 4. Bootstrap
git init
git config core.hooksPath 99-Operations/hooks
python3 -m venv .venv                                # vault-local python (PEP 668)
.venv/bin/pip install -r 99-Operations/requirements.txt
. 99-Operations/config.env                           # VAULT_ROOT + vocab + .venv on PATH

# Bootstrap render, then deploy all scripts
python3 - << 'EOF'
import re, pathlib, frontmatter, os
note = pathlib.Path("99-Operations/scripts/render-reconcile.md")
m = re.search(r"^```python\n(.*?)^```", frontmatter.load(note).content, re.S | re.M)
target = pathlib.Path(os.path.expanduser("~/bin/vault-render.py"))
target.parent.mkdir(parents=True, exist_ok=True)
target.write_text(m.group(1)); target.chmod(0o755)
EOF

python3 ~/bin/vault-render.py render
python3 ~/bin/vault_naming.py                        # emit naming-rules.json

# 5. Initial commit
git add -A
git commit -m "init: fork from value-memory-mining template"

# 6. Open vault-root in Obsidian and start mining

Full walkthrough: docs/USING-THIS-TEMPLATE.md


Operational Scripts (13)

All scripts are stored as literate meta-script notes in vault-template/99-Operations/scripts/ and deployed to ~/bin/ via render.

ScriptClassSchedulePurpose
vault_naming.py[script]manualNaming ruleset SSOT; emits naming-rules.json
pre-commit[script]git hookBlocks commits with naming-violating filenames
vault-render.py[script]manualDeploy / reconcile Layer-0 scripts
vault-daily-note.py[script]1 0 * * *Create today's daily note
vault-lint.py[script]manualFrontmatter + naming conformance
vault-orphans.py[script]manualFind Treasury notes not linked from any MOC
vault-refine-detect.py[script]0 6 * * *Queue ore that has cleared the grade gate
vault-refine-execute.py[script]manualApply approved proposals to Treasury
vault-dump.sh[script]manualMove spent husk to Spoil
vault-slag.sh[script]manualMove uneconomic effort to Tailings
vault-reprospect.py[script]manualList slagged efforts for re-evaluation
vault-rollover.py[script]2 0 * * *Append carry-over links to daily note
vault-kanban-render.py[script]manualRender Markdown kanban board

The OpenSpec Layer

This repo is governed by OpenSpec v1.4.1 using the spec-driven schema. ADRs are implemented as a project convention alongside the spec framework (see ADR-0001).

DocumentPurpose
openspec/project.mdStanding goals, 13 invariants, tech stack
openspec/constitution.mdConstitutional protection, Informed-Upheaval Protocol
openspec/adr/8 ADRs: framework choice → invariant ordering
openspec/specs/6 capability specs with protects: tags
openspec/changes/2 archived changes, 1 live (deferred), override template

Contributing

See CONTRIBUTING.md. Constitutional changes require the Informed-Upheaval Protocol — use the template at openspec/changes/templates/constitution-override/proposal.md.


License

Apache-2.0 — see LICENSE and NOTICE.

Copyright 2026 Keith Nielsen

Ver o original no GitHub

Bom para

Relacionados