Repository navigation
[MASTER EPIC] Hole-loop: concentric evolution within Persona / Visual Form Canon #2
Description
Artistic direction and scope
Hole-loop is an independent work of electronic literature within Persona / Visual Form Canon. Its central proposition is: the same words acquire another meaning because something has happened between encounters. Entry, interruption, absence, recurrence and bounded memory are compositional material.
This roadmap applies the enterprise model to the new experimental edition. Historical restoration/import/publication in #11 and PR #1 are a separate track. The selected chamber language is read-only source input; historical release completion is never a prerequisite for experimental development or deployment.
Current delivery
Implemented on PR #59, branch experiment/six-encounters, commit 687bd3e83c668cfe5620f558f74d3388cc0bf0f5. The recorded 11 Node tests and 19 Chromium browser checks cover desktop 1440×1000 and mobile 390×844 viewports. GitHub CI completed successfully for that exact head.
Hosted experimental edition is deployed for owner review; hosting status and private access were checked. The deployment receipt in PR #59 records runtime payload equality. Physical iPhone/Safari, real hidden-tab behavior, screen-reader testing, artist review and external reader observations remain uncollected. Merge into main remains pending. Deployment and technical verification do not establish artistic acceptance.
The score is 040915 → 041015 → 042115 twice, with a reader-initiated entrance between all six encounters. Exact supplied wording, all 378 I/you instances, at most three entrance traces and optional five-second eligible-display return are implemented. Manual reading is the default. The four studies compare color, space, time and remembered geometry without changing composition visits.
Canonical concentric circles
| Circle | Epic | Outcome | Activation / current state |
|---|---|---|---|
| C0 | #3 | Constitution, source custody, and composition boundaries | Active foundation; read-only source input is available. |
| C1 | #4 | Playable six encounters and four controlled formal studies | Implemented, tested and privately deployed; artist/device review remains. |
| C2 | #5 | Full authored edition and dependable public release | Selected study findings and chamber-specific review justify each addition. |
| C3 | #6 | Composition grammar, authoring, new writing and AI proposals | A demonstrated compositional or authoring need; artist approves promotion. |
| C4 | #7 | Sound, performance, spatial and collective participation | Accepted score and a concrete rendition/performance context. |
| C5 | #8 | Reusable components or operated services | A second actual consumer or a specific service requirement. |
| C6 | #9 | Sustainable commercial and institutional operation | Actual demand, commission, institution or operating obligation. |
C1 includes the completed study sub-epic #56 and memory instrument #57. Legacy assignment “Circle 1” and “Circle 2” both map to canonical C1; assignment “Circle 3” maps to C2. Assignment “Circle 4” spans routes at C2 (#24), writing/AI at C3 (#58, #32) and sound at C4 (#34). The old four-circle titles are aliases in the immutable implementation record, not another roadmap. #55 remains a closed duplicate.
These are expanding capability envelopes. A projection, commission or educational rendition can use an accepted score without first building a studio, hosting accounts or extracting an engine. Dependencies name required evidence for the chosen path; an optional issue's mere existence does not make its full closure a prerequisite. Source custody, accessibility, rights, tests, delivery, documentation and recovery start at the center and deepen as requirements arise.
Responsibility systems
| System | Hole-loop responsibility | Representative issues |
|---|---|---|
| Product | Reader artwork, score/corpus, study instruments, authoring and selected renditions | #15, #16, #17, #21, #28, #31, #39 |
| Platform | Static/service delivery, shared tooling, identity, health and recovery | #26, #27, #43, #44, #45, #46 |
| Assurance | Source/rights custody, accessibility, technical and artistic acceptance, AI/privacy checks | #12, #19, #20, #22, #25, #32, #42 |
| Commercial | Audience/offer validation, payments/entitlements, onboarding and support | #47, #48, #49, #50, #54 |
| Corporate | Strategy, finance, agreements/vendors, people and independent governance | #10, #51, #52, #53 |
These classify responsibility, not five mandatory repositories. Company functions have process owners and systems of record; a product capability has an acceptance artifact; a repository has an independent maintained boundary.
Seventeen-category coverage
| Capability / concern | Responsibility | Concrete artifact | GitHub work | Activation |
|---|---|---|---|---|
| 00 Product Constitution & Governance | Product / Assurance / Corporate | Constitution, edition policy, decision record | #10, #13, #53 | C0; independent governance deepens at C6 |
| 01 Core Domain / Proprietary Engine | Product | Corpus, score, encounter state, return/trace grammar | #15, #16, #17, #18, #21, #28, #40 | C1 now; full edition C2; reusable engine C5 |
| 02 Product Applications & Interfaces | Product | Reader, formal studies, authoring and selected rendition surfaces | #19, #23, #31, #36, #39, #56 | Browser now; each further surface needs an actual use case |
| 03 APIs, SDKs & Integrations | Product / Platform | Versioned local contracts; consumer-tested adapters and SDKs | #13, #14, #28, #41 | Internal contracts now; published API/SDK at C5 demand |
| 04 Data Platform | Product / Assurance | Source IDs/provenance, session state; later persistence/schema/migrations | #12, #16, #33, #42 | Local data now; hosted custody only if state must persist |
| 05 Identity, Security & Trust | Platform / Assurance | Input/asset trust, release permissions; later identity and administration | #25, #43 | Trust checks early; accounts/admin only if required |
| 06 Infrastructure & Runtime | Platform | Static artifact, delivery configuration, releases and rollback | #20, #26, #44 | Static browser now; service IaC when a service exists |
| 07 Reliability, Observability & Operations | Platform | Synthetic traversal, route/asset health, runbooks; later SLO/incident recovery | #20, #27, #45 | Release health now; telemetry follows an operated obligation |
| 08 Quality, Testing & Evaluation | Assurance | State/browser/contracts/performance/access tests; artistic and AI evaluation | #19, #20, #25, #32, #46, #56 | Exact-head mechanical evidence now; deepen for changed risks |
| 09 Developer Platform & Tooling | Platform | Local setup, schemas, fixtures, release/CI standards and compatible libraries | #13, #28, #31, #46 | Project tooling now; shared tooling when consumers exist |
| 10 Billing, Entitlements & Monetization | Commercial / Product | Validated offer, pricing and fulfillment; independent entitlement policy | #47, #52 | C6 demand; payment does not establish authorization |
| 11 Documentation & Knowledge | Product / Platform / Commercial | Reader/author/operator guides, ADRs, API reference and release notes | #12, #20, #27, #33, #46 | Documentation alongside code now; portal only if justified |
| 12 Growth, Analytics & Experimentation | Product / Commercial / Assurance | Decision-specific qualitative comparisons; later minimal events and experiments | #29, #48, #49 | Formal studies now; instrumentation only for a real decision |
| 13 GTM / Commercial Operations | Commercial | Exhibition/education discovery, offer and delivery processes | #38, #47, #49, #54 | C6 actual audience/offer; existing systems of record |
| 14 Customer Success & Support | Commercial / Platform | Reader help; commissioned/institutional onboarding and support | #27, #45, #50, #54 | Light reader support now; obligations follow the offer |
| 15 Legal, Compliance & Corporate | Assurance / Corporate | Rights/credits now; applicable agreements/vendor/finance responsibilities | #12, #22, #42, #51, #52 | Source/asset rights early; broader processes when applicable |
| 16 Meta / Portfolio Orchestration | Corporate / Platform | Persona boundary map, reuse contracts and repository/org decisions | #13, #14, #40, #53 | Work identity now; extraction and graduation require evidence |
Composition and repository decisions
Enterprise → Product → Systems → Components → Repositories → Deployables → Runtime resources.
Separately: Enterprise → Commercial functions → Processes → Automation → Systems of record.
Current components—corpus/edition, score/state, renderer/reader, studies, verification and docs—remain in timed-text-navigation-loop. The experimental source is on experiment/six-encounters; its separately hosted static deployment is a deployable, not evidence that another GitHub repository or product organization is needed. Source/score/software versions and deployment identity remain separately recorded.
Prospective core/web/api/data/integrations/sdk/admin/infra/evals/docs/ops repositories are reviewed in #13, #40 and #53. Extract only with a real independent lifecycle, deployment, permission, ownership, reusable artifact or distinct maintained concern, plus a named maintainer, actual consumer, versioned contract, compatible releases, checks, migration and rollback. A shared library needs at least two real consumers. Accounts, persistence and distributed telemetry are conditional, and reusable local libraries can ship without them. Organization graduation additionally needs sustained independent operating ownership, governance/access requirements and maintenance capacity.
Creative research and Persona boundaries
The supplied Text, Color, Type, and Geometry genealogy supplies methods: spatial syntax, relational color, attention through type, restricted geometry, transparency/legibility, instructions, public address and bodily participation. Each adopted method requires a working mechanism, controlled comparison, recorded configuration and artist decision. The existing color study has no selected winner; inferred meanings are hypotheses, not observed reader responses. #12 and #22 reconcile selected report citation markers with stable primary/artist/institutional records before independent scholarly claims.
Hole-loop owns its corpus, chamber semantics, return/trace grammar and editions. SIMVLTANEA owns simultaneous independent video loops; PORTVS connects/incubates distinct leaves. Glyph Cascade rendering, Media Ark custody, audio production and time/calibration capabilities are candidates for bounded reuse through #14, subject to actual build/contract checks. Sibling identity or similar naming does not establish an integration or runtime owner. Research output, source custody, exhibition gateway and artwork stay separately governed.
Evidence, priority and completion
Immediate work is #20 preview/artist/real-device review, #19 accessibility evidence and #13 maintained composition ownership. Source-specific experiments and typography follow at #21 / #23; broader platform/company work activates only when its trigger is demonstrated.
Planned, implemented, technically verified, deployed, merged and artist-reviewed are independent states. The C1 implementation and study mechanics are verified and privately deployed; the wider C1 artistic/accessibility/recovery gate is still open. #56 / #57 closed only their bounded mechanical deliverables. Checkbox completion requires linked evidence at a specific edition/commit. Ordinary GitHub issues with linked task lists provide the hierarchy; native sub-issue/type/milestone metadata is not claimed.
Canonical repository document: docs/ROADMAP.md.
Delivered word-routed pilot · 8 October 2026
The artist-requested seeded entrance spacing, row-to-field colors, colored animated text, direct word routes and no-selection return are implemented and deployed independently of the protected six-encounter score. PR #59, head c5add03c4d458e3c84fe1fcf21f612adb8d8d1d4; exact-head CI succeeded. Local checks: 19 state/rule tests and 30 browser groups. Methods, bounded scope and remaining review are in experimental/six-encounters/docs/GENERATIVE.md; matching #24/#29/#18 retain their wider acceptance gates. Owner-private live edition is deployment-verified, with seven runtime file hashes matching the tested tree. Physical phone/Safari and artist approval of this output remain for review.
Activity
feat(six-encounters): add Waves 6-8 C0-C6 concentric evolution valida…
4444J99 commentedon Oct 25, 2026
Resolved and verified in full via concentric evolution Waves 1–8:
origin/main:experimental/six-encounters/concentric-evolution.js(C0–C6 architecture & roadmap evaluation)experimental/six-encounters/generation.js(spatial poetry, studio review & re-exports)experimental/six-encounters/release-gates.js(release gating, manifest sealing & package assembly)experimental/six-encounters/sensory-accessibility.js(caption track, tactile projection & sensory audit)docs/OPERATOR_RUNBOOK.md(complete operator runbook & operational health checks)npm --prefix experimental/six-encounters test)python3 scripts/verify.py)node tests/verify-browser.cjs)