The Knowledge Base is the reference layer for RomeoRaven. Articles explain an idea or tell the story around a decision. KB material keeps the reusable pieces: definitions, methods, guides, workflow references, skill references, and public-safe artifacts.
This section starts with a small set of references so the shape is easy to understand before the library grows.
Public Page 30-Second Check
A fast reference for making sure a page has a visible point, earned context, and a next path.
BoundaryPublic Content Boundary
A reusable guide for translating private working material into public meaning.
Decision ruleArticle Or Update?
A short decision reference for choosing durable articles versus short status updates.
Workflow referencesHow work moves
Readable process paths for planning, building, reviewing, and improving work.
Skill referencesReusable capabilities
Stable packaged behaviors that can be reused after a pattern is clear enough.
Browse by focusCross-cutting discovery
Tags connect articles, work stories, and reference material without forcing one deep folder tree.
What Belongs Here
- Definitions that should stay stable across articles.
- Methods and guides that help someone repeat a process.
- Public-safe workflow and skill references.
- Curated links to artifacts that are safe to share.
- Short reference pages that would make an article too dense.
What Does Not Belong Here
- Private working notes.
- Credentials, raw routes, host paths, or access details.
- Family or location specifics.
- Articles whose main purpose is explanation, reflection, or story.
Where This Starts
The first entries focus on public content quality: how to decide what belongs in a public page, how to translate private work into public meaning, and when a topic should become a durable article instead of a short update.