railiance-fabric/workplans/archived/260702-ADHOC-2026-06-06.md
codex 7745a965f6
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
fix(workplans): qualify archived ad-hoc identifiers
The live-file pass missed these: archived ad-hocs carry a YYMMDD- filename
prefix, so the ADHOC-* glob did not match them. They still derive from the
forge, so they are live records rather than dead files.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-28 00:34:03 +02:00

34 lines
1.2 KiB
Markdown

---
id: RAIL-FAB-WP-ADHOC-2026-06-06
type: workplan
title: "Ad Hoc Fixes 2026-06-06"
domain: railiance
repo: railiance-fabric
status: finished
owner: codex
topic_slug: railiance
created: "2026-06-06"
updated: "2026-06-06"
---
> **Terminology note:** Historical text in this archived workplan may use the legacy term "workstream". The fleet term is **workplan** (`canon/standards/workplan-terminology-fleet_v0.1.md`).
# RAIL-FAB-WP-ADHOC-2026-06-06 - Ad Hoc Fixes
## Document Semantic Attractors
```task
id: RAIL-FAB-WP-ADHOC-2026-06-06-T01
status: done
priority: medium
```
Refine the concept of semantic attractors for the graph explorer: topic-like
view entities such as `security`, `development`, and `operations` that pull
repositories or other entities based on semantic closeness, initially scored
from repo `SCOPE.md` files and mapped into spring-layout strength.
Result: Added `docs/semantic-attractors.md` with the concept model, SCOPE.md
scoring approach, score semantics, layout mapping, payload shape, operator
workflow, relationship to zones, initial presets, implementation path, and open
questions. Linked the concept from the README and graph explorer contract.