RnD/EVOLV

Files

znetsixe b8cb889d87 wiki: audit + archive stale pages; refresh Home for 2026-05-11 wave

- Archived 20 pre-refactor pages to wiki/Archive/ with standard banners:
  - All 6 architecture/ pages (old _loadConfig/_setupSpecificClass internals,
    pre-refactor S88 hierarchy, deployment blueprint)
  - All 3 sessions/ logs (Apr-07 + Apr-13 session summaries)
  - findings/open-issues-2026-03.md (issues 1-5 all resolved by refactor)
  - concepts/generalfunctions-api.md (missing BaseDomain/BaseNodeAdapter)
  - concepts/sources-readme.md (empty PDF placeholder, never populated)
  - manuals/nodes/rotatingMachine.md + measurement.md (superseded by per-repo wikis)
  - Top-level SCHEMA.md, index.md, log.md, metrics.md, overview.md,
    knowledge-graph.yaml (all Apr-07 snapshot, pre-refactor)
- Kept wiki/concepts/ domain pages (ASM, PID, pump-affinity, settling, etc.)
- Kept wiki/findings/ proven results (BEP, NCog, curve-non-convexity, stability)
- Kept wiki/manuals/node-red/* (FlowFuse + Node-RED runtime docs, still current)
- Kept wiki/tools/* (utility scripts)
- Updated wiki/Archive.md index with 20 rows
- Fixed wiki/Home.md: Tier 6 was wrongly marked done; corrected to pending;
  Tier 9 updated to reflect 2026-05-11 in-progress wave

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-11 21:07:48 +02:00

3.3 KiB

Raw Blame History

⚠️ ARCHIVED — pre-refactor (Tier 1–4, 2026-05)

This page describes the architecture before the platform refactor. The current page is the per-node wiki on gitea.wbd-rd.nl/RnD or Home.

Kept for historical reference only. Do not update.

Project Wiki Schema

Purpose

LLM-maintained knowledge base for this project. The LLM writes and maintains everything. You read it (ideally in Obsidian). Knowledge compounds across sessions instead of being lost in chat history.

Directory Structure

wiki/
  SCHEMA.md          — this file (how to maintain the wiki)
  index.md           — catalog of all pages with one-line summaries
  log.md             — chronological record of updates
  overview.md        — project overview and current status
  metrics.md         — all numbers with provenance
  knowledge-graph.yaml — structured data, machine-queryable
  tools/             — search, lint, query scripts
  concepts/          — core ideas and mechanisms
  architecture/      — design decisions, system internals
  findings/          — honest results (what worked AND what didn't)
  sessions/          — per-session summaries

Page Conventions

Frontmatter

Every page starts with YAML frontmatter:

---
title: Page Title
created: YYYY-MM-DD
updated: YYYY-MM-DD
status: proven | disproven | evolving | speculative
tags: [tag1, tag2]
sources: [path/to/file.py, commit abc1234]
---

Status values

proven: tested and verified with evidence
disproven: tested and honestly shown NOT to work (document WHY)
evolving: partially working, boundary not fully mapped
speculative: proposed but not yet tested

Cross-references

Use [[Page Name]] Obsidian-style wikilinks.

Contradictions

When new evidence contradicts a prior claim, DON'T delete the old claim. Add:

> [!warning] Superseded
> This was shown to be incorrect on YYYY-MM-DD. See [[New Finding]].

Honesty rule

If something doesn't work, say so. If a result was a false positive, document how it was discovered. The wiki must be trustworthy.

Operations

Ingest (after a session or new source)

Read outputs, commits, findings
Update relevant pages
Create new pages for new concepts
Update index.md, log.md, knowledge-graph.yaml
Check for contradictions with existing pages

Query

Use python3 wiki/tools/query.py for structured lookup
Use wiki/tools/search.sh for full-text
Read index.md to find relevant pages
File valuable answers back into the wiki

Lint (periodically)

bash wiki/tools/lint.sh

Checks: orphan pages, broken wikilinks, missing frontmatter, index completeness.

Data Layer

knowledge-graph.yaml — structured YAML with every metric and data point
metrics.md — human-readable dashboard
When adding new results, update BOTH the wiki page AND the knowledge graph
The knowledge graph is the single source of truth for numbers

Source of Truth Hierarchy

Test results (actual outputs) — highest authority
Code (current state) — second authority
Knowledge graph (knowledge-graph.yaml) — structured metrics
Wiki pages — synthesis, may lag
Chat/memory — ephemeral, may be stale

3.3 KiB Raw Blame History Unescape Escape