Last updated 2026-05-03

Archive

AI-generated content

This document was generated by an AI assistant. Verify accuracy before relying on the details.

This subtree holds documentation that was true at some point but is not actively maintained. Pages here document the system as it was during the legacy AKS / Bitbucket era, before the monorepo conversion (commit 6376e7e) and before the new infra/ Pulumi project. Treat anything in here as historical context, not as current truth. If you need current truth, start at the wiki index.

What's in here

📚 Use the sidebar on the left to browse every individual page. The sections below are signposts — the sidebar is the source of truth.

Section	What it covered	Default `status:`
`functional-epics/`	Hand-written walk-throughs of business processes (rental, ticket, accounting flows). Many predate the EventBridge fanout.	`stale`
`technical-epics/`	Per-team how-tos, env-setup steps for the AKS world, stress-test reports. References Bitbucket Pipelines and Helm.	`stale`
`implicit/callback/`	Notes on implicit/callback flows.	`stale`
`productBoard/`	Product-board snapshots (rental process, ticketing).	`stale`
`data-dictionary.md`	Collection-attribute reference. Useful for naming conventions; needs cross-check against current schemas.	`stale`

Why archive instead of delete?

The legacy material has institutional knowledge that's hard to recover. Archiving keeps it greppable.
VuePress search still indexes it, so a stray query that lands on an old page won't 404.
Promoting selected pages back into concepts/ or runbooks/ is just a git mv away.

What to do if you find a useful page in here

Re-validate it against current code / infra.
If it's still relevant: rewrite it under concepts/, runbooks/, or services/ with proper frontmatter (see STYLE.md).
Update its archive copy to status: deprecated (or just delete it once the new page is in place).
Append a ## [YYYY-MM-DD] migrate | … line to adb-doc/log.md.

Why these pages don't have frontmatter

The lint script ignores archive/. Adding frontmatter to ~hundreds of legacy pages would be busywork; promoting individually-useful pages with full frontmatter is cheaper and cleaner.