Capability
Onboard in days. Trace every decision. Knowledge that endures.
One blueprint emits living onboarding curricula, governed golden paths, and a permanent ADR + BD### decision archive — not tribal knowledge, not documentation theatre, not onboarding archaeology.
What it is
Onboarding-and-golden-paths is the third leg of Archally: the knowledge-driven SDLC platform that turns the composable model into living onboarding curricula, opinionated golden-path templates (Backstage / Cortex / Port.io targets), and a permanent ADR + BCC v5 decision archive. New engineers ramp against the same model the team uses to architect, govern, and ship — not against stale wiki pages or whiteboard reconstructions.
Built on
- Curriculum-from-blueprint generation (proposed) — guided model tours per new-hire role
- Golden-path template emit (proposed) — Backstage / Cortex / Port.io bundles
- ADR + BD### decision archive (delivered) — time-travelable + evidence-linked
- Multi-view living docs (delivered) — provides the docs substrate
- MCP-backed agent-led onboarding (delivered) — new hires query the model through agents
How it works
The blueprint already holds the bounded contexts, decisions, and evidence. The curriculum generator (proposed, defining) walks the model and emits a guided tour per new-hire role: which contexts to read first, which decisions explain the architecture, which evidence backs which trade-off. Golden-path templates (proposed) emit as Backstage / Cortex / Port.io bundles. The decision archive (delivered) surfaces ADR D### + BD### as time-travelable, evidence-linked entries. New hires query the model through the MCP-backed agent: ask “why did we choose X over Y” and get the ADR + the evidence_refs + the rationale captured at decision time.
The future of software is no longer written — it is architected, governed, and continuously learned.
- 44% of organisations report developer onboarding takes >2 months thinking.EVD007
- 62% faster time-to-productivity with structured onboarding (Stack Overflow 2024) thinking.EVD008
- -55% Spotify's time-to-tenth-pull-request after Backstage rollout thinking.EVD009
- ~9% typical Backstage adoption outside Spotify — DIY portals fail at scale thinking.EVD010
Decision archive
thinking.OFF002
Architecture decisions stop being Markdown drift. Capture every architecture decision (ADR D###) and business decision (BCC v5 BD###) as first-class typed entities — time-travelable, cross-referenceable to evidence (EVD###), value-streams, bounded contexts, and migrations. MADR-compatible Markdown emit for ecosystem-tool interoperability is on the roadmap. Aligns with the community ADR ecosystem (MADR, joelparkerhenderson/ADR, UK Government ADR Framework) but goes structurally further than plain Markdown.
Onboarding curriculum
thinking.OFF001 + thinking.EVD009
Onboarding is a model-emission target, not a wiki-writing exercise. The curriculum generator walks the blueprint, ranks contexts by entry-pathway importance for the new hire's role, and emits a guided tour: starting bounded contexts, foundational decisions, the evidence trail behind the architecture, and live MCP queries the new hire can run themselves. Spotify cut time-to-tenth-PR by 55% with Backstage; Archally is the upstream model that lets that acceleration work without 9%-adoption DIY catalog overhead.
Complements your existing knowledge surfaces
thinking.EPL001 + EPL002 + EPL003
Archally is the upstream model — it complements, never replaces, the page-storage and Q&A surfaces your teams already use.
Confluence
complement — page storage + Rovo AI
Archally emits blueprint-derived docs that publish to Confluence pages; Confluence search indexes the emitted views. The upstream truth lives in the model; Confluence stays the page surface your stakeholders already read.
thinking.EPL001
Notion
complement — work OS + Notion AI
Archally emits model entities as Notion database rows: one row per offering, one row per decision, one row per bounded context. Notion stays the work-OS surface; the rows stay in sync because they originate upstream.
thinking.EPL002
Stack Overflow for Teams
complement — internal Q&A surface
Archally's decision archive emits ADR + BD### as Q&A pairs: “why did we choose X over Y” answered with the captured rationale, evidence_refs, and time-travel link. Stack Overflow for Teams stays the Q&A surface; the answers stay current because they originate upstream.
thinking.EPL003