README

17 — Standards

Naming conventions, element-spec requirements, workbook templates, and the improvement proposal framework. Apply these standards whenever adding a new service, container, script, or SaaS integration.

Core Standards Documents

Document	Description
project-standards.md	Project-level naming conventions, branch strategy, commit format, issue pipeline
infrastructure-standard.md	Mandatory requirements for every infrastructure element — RLS, monitoring, docs, AI registration
element-spec-template.md	Template for registering new elements in dev_r_services
workbook-template.md	Template for creating new audit-engine workbooks

Improvement Proposals

The improvements/ directory contains numbered proposals for infrastructure improvements. Each proposal has a status (open/in-progress/done).

Document	Description
README.md	Index of all improvement proposals
rulebook.md	Rules governing how improvements are proposed and implemented
01-backups.md	Backup coverage improvements
02-loki-logs.md	Loki log aggregation
03-secrets-management.md	Secrets management improvements
04-iac-ansible.md	IaC / Ansible coverage
05-blackbox-synthetic.md	Blackbox synthetic monitoring
06-consolidate-health-checks.md	Health check consolidation
07-status-page.md	Public status page
08-image-cve-scanning.md	Docker CVE scanning
09-ssh-hardening.md	SSH hardening
10-deployment-version-dashboard.md	Deployment version dashboard
11-cost-dashboard.md	Cost tracking dashboard
12-cert-expiry-alerts.md	Certificate expiry alerts
13-hostinger-runbook.md	Hostinger runbook improvements
14-n8n-workflow-versioning.md	n8n workflow versioning
15-infra-code-tests.md	Infrastructure code tests

Checklist: Adding a New Service

1. Add a row to dev_r_services in Supabase (compliance_workbook = 'yes', workbook_url set)
2. Enable RLS on any new Supabase tables: ALTER TABLE … ENABLE ROW LEVEL SECURITY;
3. Register error notifications: Discord webhook + GitHub issue on failure
4. Create docs/<service>-operations.md (or add a section to an existing doc)
5. If AI-powered: register in dev_r_ai_systems, update eu-ai-act-compliance.md
6. Add Prometheus scrape target if the service exposes a /metrics endpoint

Branching & Commit Standards

feat/*  ──┐
fix/*   ──┤──► dev ──► rc/vX.Y.Z ──► main (tagged)
bug/*   ──┤
plan/*  ──┘

All PRs target dev. Commit format:

{type}(#{issue-number}): {short description}

Implements: #{issue-number}

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Cross-references

• README — architectural conventions
• README — EU AI Act and infrastructure-standard compliance requirements
• README — workbook template for audit-engine