FR

The product, proof by proof

Nine stages. One real status for each.

Follow a community bond from campaign work through maturity decisions. Every stage names what software proves today, what remains partial, and what is still gated.

Proved in softwarePartialRoadmap or gated

The lifecycle rail

Choose a stage and keep its limits visible.

With JavaScript, the rail opens one panel at a time. Without JavaScript, all nine panels remain in order. Every anchored address opens its corresponding stage directly.

  1. 01 Campaign Partial
  2. 02 Subscription Partial
  3. 03 Signature Partial
  4. 04 Settlement Roadmap or gated
  5. 05 Certificate Proved in software
  6. 06 Registry Proved in software
  7. 07 Interest Proved in software
  8. 08 Tax slips Partial
  9. 09 Elections Partial
  1. 01

    Partial

    Prepare a campaign in the organization's name

    Synthetic templates carry the organization's brand and collect an expression of interest without payment.

    Available evidence
    Automated tests cover the issuer posture and interest-only journey.
    Current limit
    Issuer domains and any real operation remain gated pending validation.
    View dated #573 evidence, P13
  2. 02

    Partial

    Build a file without a purchase journey

    The synthetic pipeline structures the amount, series, and file documents before any money step.

    Available evidence
    Pipeline states and their refusals are tested in software.
    Current limit
    The real investor journey and personal-information collection are not activated.
    View dated #573 evidence, P3, P13
  3. 03

    Partial

    Require signature before certificate issuance

    The state machine refuses the certificate gate when the subscription is not signed.

    Available evidence
    The signed-then-settled transition is exercised in the pipeline test battery.
    Current limit
    The e-signature provider choice and live activation remain operator-gated.
    View dated #573 evidence, P3
  4. 04

    Roadmap or gated

    Confirm settlement before any issuance

    The software distinguishes a pending payment from confirmed settlement and keeps the certificate gate closed between them.

    Available evidence
    Pre-settlement refusal and the registry-certificate transaction are tested.
    Current limit
    Real payments are not activated. Enabling them requires a separate human validation.
    View dated #573 evidence, P3
  5. 05

    Proved in software

    Issue only after signature and settlement

    The certificate gate lives in one transactional boundary and rejects every incomplete file.

    Available evidence
    Tests prove that a certificate implies signed and settled, in that order.
    Current limit
    The proof covers software and synthetic data; it does not announce a real issuance.
    View dated #573 evidence, P3
  6. 06

    Proved in software

    Maintain a registry isolated by organization

    The registry records bonds in the same transaction as certificate issuance.

    Available evidence
    The transaction and cross-organization isolation battery are tested in the repository.
    Current limit
    Production use with real information remains subject to privacy gates.
    View dated #573 evidence, P3, P9
  7. 07

    Proved in software

    Calculate interest exact to the cent

    Amounts are represented in integer cents and rounding rules live in one shared engine.

    Available evidence
    Money-engine properties and schedules are tested without introducing a second calculation on this page.
    Current limit
    This page describes existing evidence; it neither calculates nor promises a return.
    View dated #573 evidence, P2
  8. 08

    Partial

    Prepare slips without claiming production readiness

    T5 and Relevé 3 work exists in the registry service with its remaining gap named in code.

    Available evidence
    The dated evidence points to the structured generation path and current tests.
    Current limit
    External validation and real tax use remain incomplete.
    View dated #573 evidence, P4
  9. 09

    Partial

    Require an explicit maturity decision

    The journey records repayment, renewal, or a donation intention without a preselected option.

    Available evidence
    Tests exercise explicit choices and the absence of an automatic default.
    Current limit
    Real donation execution and receipts remain subject to legal and operational validation.
    View dated #573 evidence, P6

An answer for each responsibility

The same evidence answers different questions.

What executive leadership can verify

The journey shows where software is demonstrated and where human validation remains mandatory. Leadership can distinguish durable capability from real activation.

What the treasury team can follow

States separate signature, settlement, and certificate issuance. The registry and interest path reuse the integer-cent engine; this page adds no financial calculation.

What the board can ask for

Every stage carries one status, a visible limit, and a link to the dated evidence inventory. A target never becomes a result in the presentation.

What an investor would experience

The intended journey makes every decision explicit, from subscription through maturity. The portal and real operations remain absent until their launch gates are cleared.

Scope of this showcase

Demonstrated on synthetic data, with no implied live activation.

This page solicits no investment, collects no personal information, and makes no payment, investor portal, or real send available. Links to those destinations remain absent until their routes exist.