GitHub Publication Record

Date: 2026-09-24

Organization: fluzo-labs

Administrator: jmanuelcorral

This record identifies provisioned resources. GitHub issues and workflow runs, not this document, own current delivery status. There is no implemented or released Fluzo runtime yet.

Published Resources

Both repositories are public, have MIT notices for Jose Corral, community documents, issue/PR templates, a named code owner and private vulnerability reporting enabled. The implementation workflow validates bootstrap metadata only; it does not claim Rust/runtime validation. Documentation builds use mdBook 0.4.52 and mdbook-mermaid 0.15.0, with workflows pinned to action commits.

HTTP checks confirmed the index, PRD, architecture and organization pages were served successfully. Browser inspection confirmed four rendered Mermaid diagrams and no Mermaid error markers. Local checks parsed examples and validated the dependency graph. These are publication checks, not acceptance of the MVP.

Issue Mapping

There are 28 implementation issues and 5 documentation/governance issues. All carry seed IDs, baseline links, acceptance briefs, type/area labels and the repository's MVP milestone. Their 60 dependencies are linked in the bodies and as GitHub-native blocked-by relationships. Consult the live issues for state.

Import Tool

The script in scripts/sync_backlog.py is dry-run by default. It detects existing seed IDs rather than overwriting issue bodies or creating duplicates. An explicit apply invocation requires a published immutable documentation baseline. Native dependency creation is separately selected and never removes existing edges.

python3 scripts/sync_backlog.py
python3 scripts/sync_backlog.py --apply --link-dependencies \
  --baseline 60c5b0732fb710cdf705476cee8d9156a5ecd971 \
  --report .tools/backlog-import.json

No token is written to a report or repository. The script invokes the already authenticated GitHub CLI; it does not request credentials itself.

Fluzo Delivery Project

The account owner completed Project authorization directly with GitHub on 2026-09-24. The public organization-level Fluzo Delivery Project now links both repositories and contains all 33 existing issues, without duplicating or rewriting them. Native dependencies remain the same 60 relationships.

Six fields are configured: Status, Priority, Delivery, Area, Size and Blocked. Status has Backlog, Ready, In progress, In review and Done. Priority, Delivery and Area reflect the seed plan. Initial Status reflects known completion or active work; Blocked reflects open prerequisites. Size and assignees remain unset rather than inventing estimates or allocating people.

These are views of the same issues, not separate boards to synchronize. Blocked and Ready need maintainer triage when dependency states change; no automatic scheduling or continuous dependency-field refresh is implied. Project creation does not start implementation or authorize a release. Governance evidence and the reviewed publication update are tracked by ORG-02.