2026-08-11 — Edit registry for tektree-io

rank: decision outranks: []

2026-08-11 — Edit registry for tektree-io

Date: 2026-08-11 Status: ratified Verb: petrova_act_registry_edit Slug: tektree-io MR-compliance: MR-4, MR-7, MR-12

Rationale

Replaces the blanket integrations_applicability set written by the 2026-05-13 bulk sweep, which marked all five not_applicable identically across chronicle-hq, aphelion-craft, v01t-io and cookr-hq — swept, not decided. traceo:optional because tektree-io/docs already carries 12 mermaid diagrams across ARCHITECTURE_OVERVIEW.md, EVENT_CATALOG.md and MONETIZATION_STRATEGY.md, so a live corpus had been marked inapplicable. ares:optional because petrova_onboard and petrova_install_playbook install two workflows during onboarding, so workflow runs begin existing. rocky:optional because not_applicable silently suppresses governance-stone emission in every phase verb. crumb and eva stay not_applicable for distinct, stated reasons.

Change summary

registry.yaml > repos[tektree-io] after this verb:

- slug: tektree-io
  url: https://github.com/tektree-io/docs
  default_branch: main
  role: scaffold
  profile: standard
  fleets_allowed: []
  added: '2026-05-13'
  integrations_applicability:
    ares: optional
    traceo: optional
    crumb: not_applicable
    rocky: optional
    eva: not_applicable
  notes: |
    16-repo portfolio; docs is primary. Only tektree-io/docs is governed — the other 15 repos (7 Go services, 2 frontends, 3 libs, 2 infra) are ungoverned by decision, matching the chronicle-hq / aphelion-craft one-primary-repo-per-org precedent. The workspace root is not a git repo and cannot carry a slug.

    integrations_applicability decided 2026-08-11, replacing the blanket not_applicable set written by the 2026-05-13 bulk sweep (identical across chronicle-hq, aphelion-craft, v01t-io, cookr-hq — swept, not decided). traceo:optional because the repo already carries 12 mermaid diagrams across ARCHITECTURE_OVERVIEW.md, EVENT_CATALOG.md and MONETIZATION_STRATEGY.md; the sweep had marked a live corpus inapplicable. ares:optional because petrova_onboard and petrova_install_playbook install two workflows, so workflow runs begin existing at onboarding. rocky:optional because not_applicable silently suppresses governance-stone emission in every phase verb. crumb:not_applicable — no src/content/cards corpus, architecture prose only. eva:not_applicable per the estate-wide rule at registry.yaml:314.

    profile=standard retained. fleets_allowed:[] is the operative lock — it refuses all agent automation regardless of profile (_helpers.ts:100-126), so strict would forbid only an auto-merge path that is already unreachable. permissive would remove the sole profile-level brake on a repo whose architecture decisions are consumed by 15 sibling repos.

    Applicability rationale recorded consumer-side at docs/decisions/2026-08-11-petrova-onboarding.md, which .petrova/contract.yaml cites as not_applicable_decision_doc for crumb and eva (both review_by 2027-08-11). Landed in tektree-io/docs PR #3 alongside the bootstrap artefacts.

    contract_sha absent until the onboard PR merges and .petrova/contract.yaml exists to hash.

Envelope

idempotency_key: 91b00cfdefc6156e4f9aaeb4c3ac103624168cc8b074ba4d648fa87d55525e7d
schema_fingerprint: 527e83bf1a3b
actor: human:alex@devarno.com
triggered_by:
  kind: human_request
  ref: tektree-io-applicability-2026-08-11
applied_at_iso: '2026-08-11T16:33:05.933Z'

Sign-off

Human merge required per MR-12 — this PR is opened with the awaiting-human-merge label and does not auto-merge.