33 lines
4.7 KiB
Markdown
33 lines
4.7 KiB
Markdown
# Project North Star: GEWU
|
||
|
||
**Tagline:** Investigate. Connect. Remember.
|
||
|
||
**Name:** GEWU (格物) draws on *géwù zhìzhī* (格物致知), a classical phrase commonly rendered as investigating things and extending knowledge. Its interpretations vary across traditions. Here it evokes examining sources, connecting evidence-backed ideas, and preserving what teams learn for reuse.
|
||
|
||
GEWU is a local-first, multi-project knowledge base for people and AI agents. It turns collected sources into scoped, evidence-backed notes and linked syntheses that remain traceable, reviewable, and reusable across projects and tools.
|
||
|
||
## Core Mission
|
||
|
||
Help project teams find and reuse trustworthy knowledge without losing its source, scope, freshness, or uncertainty. People search, explore and read knowledge through a read-only web UI. Local agents running in Codex, Claude, Antigravity and OpenCode retrieve cited, budgeted results and contribute exclusively through typed MCP proposals. The service validates and automatically accepts eligible proposals under owner-defined policy; humans do not approve every knowledge change. Development runs locally first, with the shared service deployed to the owner’s VPS afterward.
|
||
|
||
Initially GEWU contains no reasoning agent. It stores original source artifacts or explicit reference-only records, exposes traceable citations, and lets people navigate problems, approaches, concepts and their connections without an agent running. Local agents perform interpretation and propose new knowledge and relationships. Tags support filtering; typed links explain how nodes relate.
|
||
|
||
The initial pilot serves up to five people across 'Dome interactive content' and an 'Interactive Video Platform/Service'. Start with a smaller pilot while retaining the full v1 requirements. Human roles are admin, editor and viewer; editing uses MCP proposals under the read-only web target. Each local agent has its own revocable API key and stable identifier for attribution. Same-agent extraction and support assessment are allowed with recorded assessments and quality sampling. All team members initially read all projects; restricted project access is a later phase.
|
||
|
||
## Invariant Non-Negotiables
|
||
|
||
1. **Evidence before assertion**: Every claim and datapoint must trace to a source and a quote location. Validation checks the evidence against the archived source when available; unsupported interpretations remain clearly identified as interpretations.
|
||
2. **Project scope is explicit**: Every node belongs to one registered project or the shared library. Cross-project relevance is represented through explicit typed links and project-specific lens fit, never by silently copying or blending project knowledge.
|
||
3. **Humans own project intent**: Project owners control the north star, key questions, and autonomy policy. Agents can propose changes, but cannot directly change those human-owned goals.
|
||
4. **Proposals are the write boundary**: Local agents submit changes to staging through MCP. Eligible proposals can be accepted automatically under the configured policy; exceptions remain reviewable through the local agent workflow. Shared validators enforce schemas, scope, link rules, and evidence requirements before a proposal can be accepted into the knowledge base.
|
||
5. **Git files are the source of truth**: Markdown and YAML records remain directly inspectable and versioned. Search indexes are derived, disposable, and rebuildable from those files.
|
||
6. **One core, multiple interfaces**: The read-only UI/HTTP API, maintenance CLI and MCP server use one scoped core. Knowledge contributions enter exclusively through MCP proposals; no interface grants an unvalidated write path or exposes raw database queries.
|
||
7. **Trust survives change**: Preserve history and audit records; link contradictions instead of overwriting them; retain superseded knowledge; and disclose staleness whenever dated information is retrieved.
|
||
8. **Local-first and agent-agnostic**: The system remains useful with local files and local models, runs across Windows, macOS, and Linux, and does not depend on any one agent harness or vendor integration.
|
||
9. **Replaceable modules**: Development separates responsibilities behind explicit public contracts. Service components, local-agent capabilities, skills, pipelines and UI modules can be updated or replaced through tested compatibility and migration paths without rewriting unrelated parts of the system.
|
||
|
||
## Definition of Success
|
||
|
||
A person or agent can answer a project question with a useful, cited result in the intended time and token budget; merged claims have valid evidence; stale datapoints carry warnings; and knowledge can be reused across projects without losing its origin or confusing its scope. The measurable v1 targets are maintained in [the PRD](PRD.md#success-metrics).
|
||
|