doc	README
audience	human agent
status	living
owner	engineering
last_reviewed	2026-07-30

Engineering

What is this?

The source of truth for how we build software: coding standards, architecture, PR guidelines, RFCs, ADRs, templates, prompts, skills, and machine-enforceable rules.

Why does it exist?

So humans and AI agents share one brain. People onboard and align here; agents read it to enforce conventions, remember decisions, and assist with reviews.

Who is it for?

• Engineers contributing to any TrueLogics codebase
• Agents (Engineering Kernel, Engineering Review, PR Babysitter, Skill Registry)
• Anyone proposing a significant technical change

Current status

Planning — docs and rules are placeholders. Expand as patterns solidify.

Roadmap

1. Flesh out CODING_STANDARDS.md, ARCHITECTURE.md, and rules/
2. Adopt RFC/ADR flow for contested changes
3. Wire rules into Engineering Review and PR Babysitter

Company-wide priorities: see roadmap/.

Contributing

See CONTRIBUTING.md. Significant changes go through an RFC, then an ADR. Trivial edits: open a PR. Follow CODE_OF_CONDUCT.md and PR_GUIDELINES.md.

Map

engineering/
├── CONTRIBUTING.md / CODE_OF_CONDUCT.md / STYLE_GUIDE.md
├── CODING_STANDARDS.md / ARCHITECTURE.md / PR_GUIDELINES.md
├── KERNEL_POLICY.md / PRODUCT_DEVELOPMENT.md
├── RFC/  ADR/  templates/  prompts/  skills/  rules/

Read next: ARCHITECTURE.md → CODING_STANDARDS.md → PR_GUIDELINES.md