Skip to content
@fiducia-cloud-test

fiducia-cloud-test

fiducia-cloud-test

Independent black-box acceptance and release-certification organization for fiducia-cloud.

Live portfolio

The 2026-08-05 audit records 43 repositories:

  • 1 organization governance repository;
  • 10 language-specific SDK E2E repositories;
  • 21 focused API, consensus, coordination, scheduler, routing, discovery, messaging, WebSocket, memory, identity, telemetry, edge, sync, control-plane, Lambda, payments, infrastructure, CLI, and MCP suites;
  • 10 clean client-consumer repositories; and
  • 1 package-ingestion matrix.

Repository count is not a quality metric. The fleet is being reconciled from generated test-plan scaffolds into executable, evidence-producing probes. A schema check, source-pin check, clean skip, missing route, or workflow that only prints its profile is not product certification.

Coverage maturity

Level Meaning Release evidence?
L0 declared plan and source pins no
L1 harness/schema self-test no
L2 real product artifact launched locally and asserted development only
L3 multi-component or multi-node local execution release-candidate input
L4 independent test-org probe against pinned artifacts yes, for that topology
L5 destructive, scale, security, partition, or recovery lane yes, for that failure envelope
L6 staging/production-like certification with retained attestation release gate

Skipped or blocked work never increases maturity.

Test-program contract

fiducia-cloud/fiducia-e2e is the cross-system orchestrator. Repositories here remain independently versioned probes and consumer harnesses; they should reuse shared contracts without becoming copies of the orchestrator.

Planning and delivery

Linear is the single planning authority for both organizations. The test organization retains its own GitHub Project, repositories, CI history, workflow runs, immutable source pins, and evidence bundles so black-box acceptance remains independently attributable. Do not create work in the canceled fiducia-cloud-test (superseded) Linear shell.

Planning and governance

Repositories in this organization use semantic conflict resolution with 3–10 relevant prior commits when useful, full cross-repository context, pull-request delivery, and a hard automated-agent denylist for destructive or history-rewriting operations.

Repository relationship registry

fiducia-cloud-test declares repository roles, dependency edges, cross-organization capabilities, deployment ownership, and the git-submodule/Zed-package contract:

The public registry withholds private repository names and edges.

Popular repositories Loading

  1. .github .github Public

    Governance and reusable test workflow policy for fiducia-cloud-test.

    Python

  2. fiducia-typescript-client-e2e fiducia-typescript-client-e2e Public

    Generated sdk-consumer test harness for fiducia-cloud-test.

    JavaScript

  3. fiducia-python-client-e2e fiducia-python-client-e2e Public

    Generated sdk-consumer test harness for fiducia-cloud-test.

    JavaScript

  4. fiducia-go-client-e2e fiducia-go-client-e2e Public

    Generated sdk-consumer test harness for fiducia-cloud-test.

    JavaScript

  5. fiducia-rust-client-e2e fiducia-rust-client-e2e Public

    Generated sdk-consumer test harness for fiducia-cloud-test.

    JavaScript

  6. fiducia-java-client-e2e fiducia-java-client-e2e Public

    Generated sdk-consumer test harness for fiducia-cloud-test.

    JavaScript

Repositories

Showing 10 of 37 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…