Workspace Orientation

Repository Map

Repositories inside this directory:

ansible-collection-dnd: the rakestraw.dnd collection that bundles and distributes the pipeline suite.
ansible-role-dnd-pipeline: independent source repository for the suite-level role exposed by the collection as rakestraw.dnd.pipeline.
ansible-role-{narratio,notarius,audita,seriatim,scriptorium}: standalone application roles.
assets/campaigns: D&D campaign registry content deployed by the pipeline role.
assets/narratio-prompts: PromptKit-compatible prompts and schemas deployed for Scriptorium by the pipeline role.
assets/configs: snapshots of application configuration from a test machine; treat them as non-authoritative operational references that may use obsolete syntax or installation-specific values.
rakestraw-ansible: working deployment repository containing the pipeline_dnd proof of concept; treat it as read-only reference unless the task explicitly includes it.

Relevant upstream repositories are siblings of this directory:

../{narratio,notarius,audita,seriatim,scriptorium}: application source and authoritative application contracts.

Use the workspace inventory as the complete machine-readable inventory of paths and remotes.

Workspace conventions: normative workspace-wide rules and policy routing.
Ansible house style: normative role, collection, and application-configuration practices.
Testing house style: normative behavioral-testing practices.
Planning policy: normative feature planning and progress workflow.
MVP roadmap: settled MVP scope, architecture, and open design work.
Feature roadmaps: durable scope and target state for selected units of work.
Workspace status: current cross-repository progress and next work.
Decision records: durable rationale for significant architectural choices.
Implementation plan: the fixed location for the active staged plan or, when no plan is approved, a pending-plan notice.
Application repositories: CLI, configuration, build, and integration contracts.
Asset repositories: authoritative campaign and prompt-library content and layout.
Reference configurations under assets/configs: evidence of prior operational choices, never an application contract or a source to copy verbatim.
Individual Ansible repositories: implementation and repository-local tests.