docHub

D-061 — FreshCards canonical location is studio/modules/freshcards/, not a standalone repo

Status: accepted Date: 2026-06-23 Decided by: Helper Mavis (session 412100071272671), based on direct GitHub API check


Context

Memory (2026-06-19) said: "Pushed studio/modules/freshcards/ to avidtech6/freshcards main at commit 3d0201a. The freshcards repo's chip module had a placeholder pointing at FVS for the real implementation. Now both sides are aligned."

Memory (2026-06-22) noted: case-variant repo pair avidtech6/freshcards (lower) and avidtech6/FreshCards (upper) share storage on disk. After the dup-cleanup incident on 2026-06-22, both URLs return 404.

A direct GitHub API check on 2026-06-23 confirms:


Decision

The canonical FreshCards code lives at avidtech6/freshvibestudio/studio/modules/freshcards/. The standalone avidtech6/freshcards repo no longer exists and should not be referenced as canonical. Future FreshCards work — docHub pages, project files, plan documents — references the FVS Studio path only.


Consequences


Pact cross-references

Pact ref — freshcards-canonical-001 (studio/modules/freshcards/module.json)

path: modules/freshcards/, lineage.based_on: pact/platform/cards/cards.md + pact/freshvibe-way-v7/23-two-view-substrate.md

Relation to this decision: the path field locates the canonical substrate inside FVS Studio, not in a separate repo. This is the field that resolves the "where does FreshCards live?" question.


Related decisions


← back to Mavis workshop