Cards and Portable Workflows

Identity, content, and context

CinterForge Cards are designed to connect an item’s identity with its media or payload reference, descriptive metadata, provenance, and version lineage. The working notes call the identity UCI. Its expansion, guarantees, and lifecycle rules are being confirmed, so this page stays at the architectural level.

A collection-centered workflow

The product loop can begin with ingesting material, creating or enriching a Card, collecting related work, or viewing it. Collection is the Desktop hub; Companion centers on managing and viewing the collection. Cinter and Forge are connected workspaces for local AI/RAG and Card creation.

Interoperability with clear boundaries

Cards are intended to connect supported workflows, including handoffs to independent Open Apps. Interoperability is specific to each app, Card type, and format. The team should document each verified path—source, operation, resulting file or Card, and any provenance retained—rather than implying universal portability or automatic conversion.

The detailed Card model and How Cards Work explain the user-facing concepts. The taxonomy and codes remain in product review until Product and Engineering confirm the schema.