Skip to content

Define owner-controlled composition and complete customization walkthrough #43

Open

Description

@jdylanmc

This was generated by AI during triage.

Current status (2026-09-29)

Inspected baseline: main@b64bb2f.

Status: owner-controlled composition scope still needs a product decision.

The persistent catalogue, category/title/theme settings, default generated Repository view, existing serve command, static bundles, and npm delivery are implemented. There is one Archify shell, not a missing second explorer.

Remaining acceptance

  • Agree the bounded composition/extensibility requirement beyond existing presentation settings before implementation.

  • Perform and retain the manual customization walkthrough: configuration changes and observed outcomes. Automated settings tests are not evidence that a manual walkthrough occurred.

  • Preserve the single shell, actual renderer boundary, source/authored distinctions, and owner-managed hosting.

Broader curated-view predicates/composition remain coordinated with #9. No addon marketplace, hosted authoring, authentication, or restoration of WebGL is implied. Cross-machine verification and replacement exploration are not missing prerequisites.

Evidence: catalogue configuration, repository exploration, and maintained requirements.

Previous issue text and original requirements (historical; current disposition is above)

Reconciled status (2026-09-27)

Inspected baseline: main@c8e22ec. Maintained intent: docs/product-spec.md.

Disposition: remains open for the scope below.

Complete committed-story inventory, empty-state behavior, existing-server integration, bounded catalogue settings, and the persistent shell are shipped. Retaining an explorer entry is superseded by #71. Keep this issue for FR-06 / AC-11 composition/extensibility and manual customization evidence preserved in the maintained specification.

Remaining scope

  • Define the bounded owner-controlled composition/extensibility requirement with the maintainer before implementing beyond the existing settings.
  • Perform and retain the required manual customization walkthrough, including configuration changes and observed outcomes; automated configuration tests are not proof that it occurred.
  • Preserve the single shell, existing serve command, real renderer boundary and owner-managed static hosting. Do not infer authorization for an addon marketplace, hosted authoring, authentication, or restored WebGL UI.

Readiness and dependencies

Remove ready-for-agent: composition scope still needs a product decision. Remove the obsolete #42 blocking relationship because story preview is already shipped; remaining cross-machine evidence is not a prerequisite for defining or exercising customization.

Merged delivery evidence: #50, #71, #78. These merge commits are ancestors of the inspected main revision.

Current source and regression evidence:

Existing exact-main CI is successful. This reconciliation inspected current code, committed regression coverage and merged history; it does not claim a new test run, manual walkthrough, visual acceptance, cross-machine experiment, or approval of paused work.

Historical issue scope (preserved; current disposition and readiness are above)

Parent

#40 - Specification: Storybook-for-architecture whiteboard MVP.

Source revision: 2026-09-19T12:09:45Z; complete specification body SHA-256 1965e96d069d64a85cb7850abde9d91249874a7cf1bd2e0b38197262a86827de.

Requirements: FR-03, FR-04, FR-06, CON-04, S-2, S-5, S-E2.

What to build

Make the product open on one generated landing page that categorizes and showcases the repository's authored stories and its generated explorer. Owners can adapt categorization, presentation, and composition through a minimal supported configuration surface, without editing topo package source. Reuse topo serve and preserve the explorer as an entry, not an independently competing front door.

Acceptance criteria

  • AC-05: The generated landing page lists every authored story and the generated explorer, organized into categories, without a hand-maintained index file.

  • AC-06: Zero authored stories still yields a coherent site containing the explorer.

  • AC-07: Existing topo serve serves the composed site on its default port and an explicit --port; do not introduce a second server.

  • AC-11: The owner can change categorization and presentation through supported configuration without changing topo source.

  • Keep customization bounded to the agreed minimal configuration/theming/composition surface; do not build an addon marketplace, hosted authoring service, authentication system, or new explorer capabilities.

Verification and readiness

  • Exercise empty, single-story, and multiple-story corpora with catalogue completeness assertions.

  • Use real CLI/browser tests for default/explicit port, story selection, and reaching the retained explorer.

  • Perform the specification's manual customization walkthrough and retain configuration examples plus observed outcomes.

Readiness: Fully specified; needs the working story preview/document path. Long-term explorer retirement and a larger extension ecosystem remain outside this slice.

Open product decisions: None for this scoped slice. Return newly discovered material scope decisions to the human.

Blocked by

A closed prerequisite alone is insufficient: its implementation must be available on this delivery's agreed base.

Boundaries

  • Scope is Specification: Storybook-for-architecture whiteboard MVP #40, not the broader historical Roadmap: deferred architecture and engineering-health capabilities #1 roadmap. Preserve existing scanner, explorer, curated views, and enrichment behavior.

  • No hosting, authentication, deployment, public npm publication, human sketch canvas, or mandatory model service.

  • No heuristic staleness or explanation-coverage gate. Structural/source validation does not prove semantic truth.

  • Use the existing unit/script/browser verification seams and keep the repository regression gates. No documentation gate is added.

  • The source snapshot for this breakdown has AC-14 already delivered by PR chore(lint): add correctness baseline #39. Begin implementation from a base containing that merged change.

  • Keep the preserved prototype unchanged. Do not silently edit the vendored renderer or substitute an unapproved upstream version.

  • The implementation owner chooses local code structure within the agreed contracts; return newly discovered material product choices to the human.

Delivery grouping

Intentionally separate coherent deliveries, one eventual PR per child; not one parent-wide implementation PR. No delivery is launched by publication.

No assignee or exclusive ownership is claimed. Publication does not authorize worker dispatch, implementation, merge, or parent closure.

Assembled acceptance

The complete parent acceptance remains all AC-01 through AC-19 over the assembled state. Independent child completion is not a claim that the full MVP is shipped. The final delivery owner verifies the complete local authoring, composition, linked navigation, and static bundle journey once all prerequisite changes are on the agreed base. Parent closure and merges remain human-owned.

Activity

  1. added a commit that references this issue on Sep 20, 2026
  2. changed the title [-]Browse and customize a generated story catalogue alongside the explorer[/-] [+]Define owner-controlled composition and complete customization walkthrough[/+] on Sep 27, 2026
  3. jdylanmc commented on Sep 27, 2026

    @jdylanmc
    OwnerAuthor

    Backlog reconciliation (2026-09-27)

    Inspected baseline: main@c8e22ec. Maintained intent: docs/product-spec.md.

    Disposition: remains open for the scope below.

    Complete committed-story inventory, empty-state behavior, existing-server integration, bounded catalogue settings, and the persistent shell are shipped. Retaining an explorer entry is superseded by #71. Keep this issue for FR-06 / AC-11 composition/extensibility and manual customization evidence preserved in the maintained specification.

    Remaining scope

    • Define the bounded owner-controlled composition/extensibility requirement with the maintainer before implementing beyond the existing settings.
    • Perform and retain the required manual customization walkthrough, including configuration changes and observed outcomes; automated configuration tests are not proof that it occurred.
    • Preserve the single shell, existing serve command, real renderer boundary and owner-managed static hosting. Do not infer authorization for an addon marketplace, hosted authoring, authentication, or restored WebGL UI.

    Readiness and dependencies

    Remove ready-for-agent: composition scope still needs a product decision. Remove the obsolete #42 blocking relationship because story preview is already shipped; remaining cross-machine evidence is not a prerequisite for defining or exercising customization.

    Merged delivery evidence: #50, #71, #78. These merge commits are ancestors of the inspected main revision.

    Current source and regression evidence:

    Existing exact-main CI is successful. This reconciliation inspected current code, committed regression coverage and merged history; it does not claim a new test run, manual walkthrough, visual acceptance, cross-machine experiment, or approval of paused work.

  4. added
    enhancementNew feature or request
    decisionAn open design decision that must be resolved
    needs-triageMaintainer evaluation needed
    on Sep 29, 2026
  5. jdylanmc commented on Sep 29, 2026

    @jdylanmc
    OwnerAuthor

    This was generated by AI during triage.

    Backlog reconciliation (2026-09-29)

    Refreshed delivered shell/exploration/distribution context while retaining the actual remaining composition decision and manual customization walkthrough. Kept this out of the ready-for-agent queue.

    Evidence and preserved historical requirements are in the updated issue body. Baseline: main@b64bb2f. No repository source or credential changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    decisionAn open design decision that must be resolvedenhancementNew feature or requestneeds-triageMaintainer evaluation needed

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions