jordan/stemedb
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
a776744889
stemedb/.claude/skills/stemedb-core/SKILL.md
jordan a776744889 Initial project setup with Claude Code monorepo structure 
- Rust workspace with stemedb-core crate
- Full .claude/ configuration (agents, skills, commands, guides)
- ai-lookup/ for token-efficient fact storage
- Quality gates: clippy, fmt, jscpd duplication detection
- Pre-commit hook with 5-phase quality checks
- CLAUDE.md router and CODING_GUIDELINES.md standards

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-31 10:56:26 -07:00

1.2 KiB
Raw Blame History

name description
stemedb-core Core guidelines for the Episteme database engine. Use when working on storage, DAG, or assertions.

StemeDB Core Guidelines

Identity

You are building the Spine of Episteme. This is the storage engine that persists the Merkle DAG.

Principles

  • Append-Only: We never mutate an existing Assertion. We only append new ones.
  • Content-Addressed: The ID of an assertion is its Hash (BLAKE3).
  • Defensive: Use quarantine-journal patterns (WAL, Fsync).
  • Typed: Use Strong types (EntityId, RelationId, Hash) not Strings.

Data Structures

Assertion

pub struct Assertion {
    pub subject: EntityId,
    pub predicate: RelationId,
    pub object: ObjectValue,
    pub source: SourceHash,
    pub agent: AgentId,
    pub timestamp: u64,
}

Storage Layout (KV)

  • H:{Hash} -> Assertion (Main Store)
  • S:{Subject} -> Vec<Hash> (Index)
  • SP:{Subject}:{Predicate} -> Vec<Hash> (Index)

Do

  • Use rkyv for zero-copy deserialization.
  • Use thiserror for library errors.
  • Validate signatures on Ingest.

Do Not

  • Use unwrap() in core logic.
  • Store large blobs in the Assertions (store pointers/hashes instead).