Skip to content

Knowledge Base Guide

How to add and organize content in the Minnova knowledge base.

Quick Reference

I want to... Do this
Add a new client Copy docs/clients/_template/ to docs/clients/{client-name}/
Log daily work Add entry to docs/clients/{client}/journal/{YYYY-MM-DD}.md
Document a meeting Copy docs/operations/meetings/_template.md to docs/operations/meetings/{year}/{YYYY-MM-DD}-{topic}.md
Add a decision Include in meeting notes or client README
Research a topic Add to docs/projects/ or docs/playbooks/

New Client Setup

When a new client engagement starts:

  1. Create client folder:
cp -r docs/clients/_template docs/clients/{client-name}
  1. Fill in README.md:
  2. Client name and description
  3. Tech stack (as you learn it)
  4. Key features/scope

  5. Links to repos, boards, environments

  6. First meeting:

  7. Create journal/{YYYY-MM-DD}.md with kickoff notes
  8. Or use meeting template if it's a formal meeting

Daily Journal

Each client has a journal/ folder for daily notes.

When to write:

  • End of work session
  • After significant progress or blockers
  • After calls or discussions

Format: journal/{YYYY-MM-DD}.md

# {YYYY-MM-DD}

## Done

- {What you accomplished}

## Notes

- {Observations, learnings, context}

## Blockers

- {What's stuck, needs input}

## Next

- {What's planned next}

Keep it brief. The goal is future recall, not exhaustive logging.

Meeting Notes

For structured meetings (client calls, planning, vendor discussions):

  1. Copy template:
cp docs/operations/meetings/_template.md \
   docs/operations/meetings/{year}/{YYYY-MM-DD}-{topic}.md

  1. Before meeting: Fill in purpose and preparation questions

  2. During/after: Capture notes, decisions, action items

Where Things Go

docs/
├── clients/           # Per-client documentation
│   ├── _template/     # Copy this for new clients
│   └── {client}/
│       ├── README.md  # Client overview
│       └── journal/   # Daily notes
│
├── operations/        # Running the business
│   ├── meetings/      # Meeting notes
│   ├── contracts/     # Agreement templates
│   └── accounting/    # Financial docs
│
├── projects/          # Internal projects and research
│
├── playbooks/         # How-to guides
│
├── processes/         # How we work
│
└── infrastructure/    # Minnova infra docs

Tips

  • Write for future you. In 3 months, will you understand this note?
  • Link liberally. Reference other docs when relevant.
  • Keep READMEs updated. They're the entry point.
  • Commit often. Small commits are easier to review and revert.

Using with AI

When working with oracle or other AI tools:

  • The AI has access to this entire knowledge base
  • Ask it to create entries: "Create a journal entry for today's featbank work"
  • Ask it to find things: "What did we decide about authentication?"
  • Ask it to scaffold: "Set up a new client folder for Acme Corp"

The AI knows these templates and conventions. Just describe what you need.