generated from coulomb/repo-seed
tegwick
f7ad73d9da
Register the InfoTechCanon Repository Layout Standard as a domain standard (itc-repo-layout), processed from demand through the canon's Purpose/Demand intake without collapsing existing model concepts. - Register standard in artifacts/index.yaml, canon.yaml, infospace.yaml; regenerate indexes, views, briefs, tree, and validation (validate green). - T04: add reconciliation.yaml (partial/as-is dogfooding, declared core conformance, recorded tensions); resolve the demand by moving it out of demand/ to the evaluation pack as source-demand.md and removing demand/. - T05: add consumer-adoption-brief.md for downstream repos. - Update test artifact/standard counts (60->61, standards 2->3). - Mark T03/T04/T05 done; workplan and registry status -> finished. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
117 lines
5.0 KiB
YAML
117 lines
5.0 KiB
YAML
id: demand/repository-layout/intake
|
|
title: Canonical Repository Layout Demand Intake
|
|
status: reviewed
|
|
type: demand-intake
|
|
uses:
|
|
- model/purpose-demand-extension
|
|
- model/governance
|
|
source:
|
|
artifact: infospace/evaluations/repository-layout/source-demand.md
|
|
arrival_surface: demand/
|
|
arrival_note: >-
|
|
Arrived in the repo-level demand/ inbound directory, which the source
|
|
document itself defines as un-reviewed inbound. Processed here as a
|
|
DemandSignal before any canon artifact is authored.
|
|
captured_date: "2026-06-08"
|
|
resolution:
|
|
resolved_date: "2026-06-13"
|
|
moved_to: infospace/evaluations/repository-layout/source-demand.md
|
|
note: >-
|
|
Now reviewed, the raw demand left the demand/ inbound directory (per the
|
|
standard's own rule) and is retained as the captured original beside this
|
|
evaluation pack. The repo-root demand/ directory was emptied and removed.
|
|
follow_up_owner: canon
|
|
|
|
consumer_purpose:
|
|
id: purpose/canonical-repository-layout
|
|
concept: ConsumerPurpose
|
|
consumer: bernd-worsch / cross-domain (custodian, railiance, markitect, coulomb_social, personhood, foerster_capabilities, netkingdom)
|
|
anchored_in: >-
|
|
Consumer intent to make documentation across many repositories
|
|
retrieval-oriented and uniform, so humans and agents can find the right
|
|
information at the right working-memory cost.
|
|
declared_purpose: >-
|
|
A canonical, recommendation-level documentation layout for repositories —
|
|
INTENT.md / SCOPE.md plus research/, demand/, spec/, workplans/, docs/,
|
|
wiki/, issues/, history/ — with a SCOPE-to-INTENT gap-closing operating mode.
|
|
use_case:
|
|
id: usecase/uniform-doc-retrieval
|
|
concept: UseCase
|
|
description: >-
|
|
A maintainer or agent entering any conforming repository can locate
|
|
intent, current scope, raw demand, specs, active work, stakeholder docs,
|
|
collaborative wiki, mirrored tickets, and archived material by directory
|
|
convention rather than per-repo discovery.
|
|
|
|
demand_signal:
|
|
id: signal/repository-layout-recommendation
|
|
concept: DemandSignal
|
|
observation: >-
|
|
An explicit, written recommendation for a canonical repository documentation
|
|
layout, distilled from lived practice and offered to the canon to "pick up".
|
|
signal_type: explicit-request
|
|
strength: single-but-high-intent
|
|
provenance:
|
|
prior_art:
|
|
- CoulombSocial
|
|
- HelixForge
|
|
- MarkiTect
|
|
note: >-
|
|
Layout is presented as evolved best practice from these three repos'
|
|
documentation experience; yawex prior-art material is named as research/
|
|
content. Background doc types (PRD / TechSpec / UseCaseCatalog /
|
|
ArchitectureBlueprint) reference the InfoTechPrimers space on coulomb.social.
|
|
consumer_need:
|
|
id: need/uniform-retrievable-docs
|
|
concept: ConsumerNeed
|
|
description: >-
|
|
Need for a shared, low-friction documentation structure that keeps working
|
|
memory uncluttered (history/ out of daily scope) and routes inbound
|
|
demand through systematic review (demand/ -> tasks/workplans).
|
|
horizon: current
|
|
|
|
# Preliminary fit only — the binding PurposeFit / placement decision is T02.
|
|
preliminary_purpose_fit:
|
|
concept: PurposeFit
|
|
state: gap
|
|
rationale: >-
|
|
The canon owns adjacent concepts (Information Space for knowledge packaging
|
|
and retrieval; Governance + Purpose/Demand for INTENT/SCOPE/PURPOSES and the
|
|
demand/ intake surface; Task for workplans/history) but does not yet own a
|
|
named cross-cutting convention that prescribes a canonical repository
|
|
documentation directory set. This is a producer-facing convention the canon
|
|
does not currently provide.
|
|
matched_canon:
|
|
- model/information-space
|
|
- model/governance
|
|
- model/purpose-demand-extension
|
|
- model/task
|
|
- pattern/intent-scope-purposes
|
|
note: Binding fit evaluation and ownership mapping are deferred to T02.
|
|
|
|
scope_pressure:
|
|
concept: ScopePressure
|
|
state: flagged-for-review
|
|
current_scope_ref: SCOPE.md
|
|
pressure: >-
|
|
SCOPE.md currently frames the repo as a seed corpus of kernel/models/
|
|
standards/profiles/patterns and does not promise a producer-facing repository
|
|
documentation-layout convention. Adopting this demand would extend the canon
|
|
to own such a convention (working hypothesis: a new standard), so it must go
|
|
through governance scope-pressure review rather than silently expanding scope.
|
|
alignment_with_producer_intent: >-
|
|
Aligns with the canon's stated purpose of providing interoperable, retrievable
|
|
structures and seed conventions for infospaces and agent use; the convention
|
|
is recommendation-level, matching the canon's non-coercive posture.
|
|
recommended_disposition: add_standard_candidate
|
|
decision_authority: canon governance
|
|
review_gate: ITC-WP-0012-T02
|
|
|
|
disposition:
|
|
intake_outcome: accepted_for_analysis
|
|
next_step: >-
|
|
Proceed to T02 placement decision (review gate): decide canon ownership,
|
|
map each layout element to an existing model, and emit explicit placement +
|
|
extension candidates before any standard text is written.
|
|
no_artifact_authored: true
|