Snapshot data

Wednesday, August 12

Here’s the whole Ezkart picture.

Start broad. Open anything when you need the details.
Official production

Launch readiness

Needs attention
68% ready
7 days to target

Core commerce is stable. Catalog persistence and recurring billing need production decisions.

    Target 19 Aug 2026
    Owner attention

    Three decisions unlock the week

    Portfolio

    Work in motion

    Progress, confidence, blockers, and the next concrete move.

    Environment map

    Production stays calm

    Experimental work moves through a private acceptance branch.

    Production Workbench Planned
    Seller operating system

    From seller input to customer outcome

    Click a layer to understand its owner, data, dependencies, and current health.

    Last 24 hours

    Change stream

    Risk radar

    What could hurt launch

    Launch room

    One week. One ordered path.

    Every gate has an owner, proof, and decision state.
    Critical path

    Now → production

    Evidence

    Release proof pack

    Promotion workflow

    Nothing reaches production by surprise

    Project portfolio

    Track the work at any altitude.

    Filter the portfolio, then open a project for its full brief and checklist.

    System blueprints

    See what each seller owns—and how it connects.

    Follow the seller's HTML, tenant boundary, database records, and storage paths as one connected architecture.

    Git & environments

    Branches, merges, and websites—connected.

    Trace a change from its preserved snapshot through test, approval, main, and the Hostinger website that follows each branch.
    View merged PR #1 ↗
    Ezkart main Ezkart workbench tag / separate repo

    Seller structure

    One seller, every owned record and asset.

    See the storefront component tree and then drill into the exact Postgres tables, tenant keys, and object-storage paths behind it.
    Seller website composition

    Published HTML and its data sources

    The storefront is assembled from seller-owned page, catalog, and asset records.

    Tenant boundary

    The seller bucket in Postgres and object storage

    Every relationship is visible, including the seller_id boundary and conditional product-type records.

    Decision intelligence

    Surface uncertainty before it becomes damage.

    Impact, likelihood, owner, mitigation, and required decision are visible together.
    Impact × likelihood

    Risk matrix

    Owner queue

    Decision register

    System history

    A readable trail of what changed.

    Commits, deployments, decisions, tests, and project updates become one narrative.
    Portfolio tracking

    Track another project

    Create an executive-level card now; enrich its checklist from the project detail view.