import{_ as a,o as i,c as t,ag as o}from"./chunks/framework.CmQHR1bQ.js";const m=JSON.parse('{"title":"Technical Specifications","description":"","frontmatter":{},"headers":[],"relativePath":"specs/index.md","filePath":"specs/index.md"}'),r={name:"specs/index.md"};function n(s,e,c,l,d,p){return i(),t("div",null,[...e[0]||(e[0]=[o('<h1 id="technical-specifications" tabindex="-1">Technical Specifications <a class="header-anchor" href="#technical-specifications" aria-label="Permalink to &quot;Technical Specifications&quot;">​</a></h1><p>Canonical specification documents for the parpour platform.</p><p>All specification files are located at the parpour project root. This directory indexes and links to those specifications.</p><h2 id="specification-categories" tabindex="-1">Specification Categories <a class="header-anchor" href="#specification-categories" aria-label="Permalink to &quot;Specification Categories&quot;">​</a></h2><h3 id="core-specifications" tabindex="-1">Core Specifications <a class="header-anchor" href="#core-specifications" aria-label="Permalink to &quot;Core Specifications&quot;">​</a></h3><ul><li><strong>TECHNICAL_SPEC.md</strong> — Overall technical architecture and system design</li><li><strong>API_EVENTS.md</strong> — Event schema and API contract documentation</li></ul><h3 id="planning-tracks" tabindex="-1">Planning Tracks <a class="header-anchor" href="#planning-tracks" aria-label="Permalink to &quot;Planning Tracks&quot;">​</a></h3><ul><li><strong>TRACK_A.md</strong> — Track A: [Description from TRACK_A.md]</li><li><strong>TRACK_B.md</strong> — Track B: [Description from TRACK_B.md]</li><li><strong>TRACK_C.md</strong> — Track C: [Description from TRACK_C.md]</li></ul><h3 id="implementation-guides" tabindex="-1">Implementation Guides <a class="header-anchor" href="#implementation-guides" aria-label="Permalink to &quot;Implementation Guides&quot;">​</a></h3><ul><li><strong>VENTURE_SPEC.md</strong> — Venture platform specifications</li><li><strong>CIV_SIM_SPEC.md</strong> — CIV simulation specifications</li></ul><h2 id="how-to-use" tabindex="-1">How to Use <a class="header-anchor" href="#how-to-use" aria-label="Permalink to &quot;How to Use&quot;">​</a></h2><ol><li>Start with <strong>TECHNICAL_SPEC.md</strong> for the overall system architecture</li><li>Review relevant track specs (TRACK_A/B/C) for your work area</li><li>Consult <strong>API_EVENTS.md</strong> for event/API contract details</li><li>Use <strong>VENTURE_SPEC.md</strong> and <strong>CIV_SIM_SPEC.md</strong> for implementation details</li></ol><h2 id="spec-standards" tabindex="-1">Spec Standards <a class="header-anchor" href="#spec-standards" aria-label="Permalink to &quot;Spec Standards&quot;">​</a></h2><p>All specifications follow these standards:</p><ul><li>Stored at parpour project root (not in subdirectories)</li><li>Maintained in Markdown format</li><li>Include clear descriptions, diagrams, and examples</li><li>Cross-referenced with code via FR IDs and traceability markers</li><li>Updated as part of feature development (not deferred)</li></ul><p>See <a href="/parpour/QUALITY_GATES">Quality Gates</a> for enforcement of specification standards.</p>',16)])])}const f=a(r,[["render",n]]);export{m as __pageData,f as default};
