# Repository Layout Standard — reconciliation against info-tech-canon's own layout
# ITC-WP-0012-T04. Resolves placement-decision candidate/dogfood-canon-repo.
type: repo-reconciliation
workplan: ITC-WP-0012
task: ITC-WP-0012-T04
standard: standard/repository-layout
created: "2026-06-13"

decision:
  dogfood_extent: partial
  declared_conformance_level: core
  summary: >-
    info-tech-canon adopts the Repository Layout Standard at recommendation
    level, as-is. It already satisfies the core level and is not restructured to
    chase full conformance now. The infospace/ content layout is explicitly out
    of scope of this documentation-layout convention.

current_layout:
  root_documents:
    - INTENT.md        # present — Governance (Intent)
    - SCOPE.md         # present — Governance (Scope)
  directories_present:
    - demand/          # transient inbound; emptied + removed after this demand was resolved
    - spec/            # present
    - wiki/            # present
    - workplans/       # present; State-Hub-registered
    - seeds/           # repo-specific: RC seed corpus, not part of the standard's set
    - infospace/       # the concrete infospace content (distinct layout, see tension below)
    - src/ tests/      # Python service shell, not documentation directories
  directories_absent:
    - research/        # no dated explorations packaged yet
    - docs/            # stakeholder docs live inside infospace/ today
    - issues/          # no external-ticket mirror maintained here
    - history/         # finished workplans tracked via status, not yet relocated

conformance_assessment:
  minimal: satisfied        # INTENT.md + SCOPE.md at root
  core: satisfied           # + demand/ (as-needed), workplans/, docs-equivalent in infospace/
  full: not_satisfied       # research/, issues/, history/ and yymmdd- prefixes not adopted
  note: >-
    Conformance is self-declared and graded (standard §7). The canon claims
    'core' and omits directories it does not currently need.

tensions:
  - id: infospace-content-layout
    tension: >-
      infospace/ uses a kernel/models/standards/profiles/patterns CONTENT layout,
      which is a different concern from this DOCUMENTATION layout. The standard's
      §9 already calls this out; the two layouts coexist and are not reconciled
      into one.
    resolution: keep_distinct
  - id: seeds-directory
    tension: >-
      seeds/ is repo-specific (RC seed corpus) and has no slot in the standard's
      canonical set.
    resolution: out_of_scope_repo_specific
  - id: docs-location
    tension: >-
      Stakeholder/agent documentation lives under infospace/ (agent briefs,
      views, retrieval indexes) rather than a root docs/. Functionally covers the
      docs/ purpose without the directory name.
    resolution: satisfied_by_equivalent
  - id: history-relocation
    tension: >-
      Finished/canceled workplans currently stay in workplans/ with a status
      field rather than moving to history/. The standard recommends relocation.
    resolution: deferred
    note: >-
      Not adopted now to avoid churn against State-Hub workplan conventions;
      revisit if workplans/ grows large enough to clutter working memory.

dogfood_actions_taken:
  - This demand was processed through demand/ and, once reviewed, the raw file
    left demand/ for the evaluation pack (source-demand.md); the empty demand/
    directory was removed — exercising the standard's own demand-resolution rule.

not_done_now:
  - Creating research/, issues/, or history/ directories.
  - Relocating finished workplans to history/.
  - Restructuring infospace/ (explicitly a separate content-layout concern).