Documentation

Documentation architecture.md is the reference for maintainers: the module map, the two version axes, the semantic model, the capability declaration, and the invariants that must not be broken silently. Start there.

Security posture This is a REVIEW, not an audit. It was written by the people who wrote the code, from a static reading of this tree on 2026-09-25, read again on 2026-09-26 against the tree released as 0.4.0, on 20

First installation — Linux and Windows From a clean machine to a running Sandbox and Workbench. You install Java and download Ra

caql-core CaQL parser, AST and semantics. A language, not a tool. S-2: syntax and AST are major-version neutral; version-specific validation happens after parse, never in the grammar. S-3: **only scalar things bind, an

raposza-auth JWT and JWKS handling. Real tokens against real keys; no bypass mode.

raposza-bom Bill of materials. Applications will import this to get a coherent set of platform versions without pinning each one. NOT ACTIVE. The module carries a pom with no dependencyManagement and no source, i

raposza-canton Everything that knows what Canton is: installations, versions, editions, configuration and overlays, node launching, PQS/scribe. Depends on raposza-runtime. Knows nothing about sandboxes: a class that

raposza-lf Daml-LF archive decoding. A translation module; SDK types permitted.

raposza-model Project-owned domain types: the LF and contract semantic core. No SDK types. No dependency on any target module, and none on raposza-spi either - the direction is one way, and that is what the split is

raposza-runtime Process supervision, embedded PostgreSQL, the free-port guard, health and lifecycle ordering. Nothing here knows what Canton is. A class that names a Canton version, an edition, a HOCON key or a par

raposza-sandbox What a sandbox IS: the STACK. Two of them - a 3.x SandboxStack and a 2.x Sandbox2xStack - plus the sandbox spec, the launcher choice, and the process that runs Canton's own sandbox subcommand. Eve

raposza-spi The translation service-provider interface, and the machine-readable capability declarations. LedgerClient_i and LfDecoder_i live here because a translation target implements them. raposza-model holds

raposza-target-2x Translation implementation for Canton 2.9 and 2.10, over Ledger API v1. This is the complete client implementation: participant identity, parties, users, the active contract set, single contracts, tra

raposza-target-3x Translation implementation for Canton 3.4 and 3.5, over Ledger API v2. Target3x is discoverable through ServiceLoader, and its connect() returns Lapi2Client, the Ledger API v2 client. What a 3

raposza-test-idp Local test identity provider. Must be structurally incapable of reaching a production configuration. What it serves GET /.well-known/openid-configuration issuer, token_endpoint, jwks_uri GET /jw

Platform Shared modules, released together under one version. Boundary rule S-1 Vendor SDK types - Canton, Daml-LF, protobuf and gRPC - are confined to the modules whose job is translating between a vendor API and t

Raposza Tools **New here? Start with FIRST_INSTALL.md** — from a clean machine to a running Sandbox and Work

Raposza - the long description Developer tooling for teams building applications on Canton. README.md is the short front page. BUILD_AND_INSTALL.md is the step by step from a clone to a running window. SECURITY.md

Security Reporting a vulnerability Write to info@raposza.com. Say what you found, how to reproduce it, and what you think it lets an attacker do. You will get an acknowledgement; if the finding is valid you will

Raposza Tools 0.6.3 — skill document for an AI assistant This document is written for an AI assistant, such as Claude, that guid

Docs App Sub-Spec Overview The docs app (@sigilry/docs) builds and publishes developer documentation for the monorepo. Scope - Build Astro/Starlight documentation content. - Publish API reference artifacts and site navigation. - Support local docs development and preview workflows. Key

Daml contract source - sigilry/sigilry/examples/demo-app/daml/TodoList.daml module TodoList where template TodoItem with owner : Party description : Text completed : Bool where signatory owner choice Complete : ContractId TodoItem controller owner do create this with completed = True choice

Sigilry Demo App This directory documents the first SDK implementation example for Sigilry. It is written for developers new to Canton/DAML who want a clear, runnable reference and well-commented patterns they can copy into their own apps. Docs site: https://sigilry.org Demo App Overview Th

Demo App Spec Overview examples/demo-app is the integration reference app for local development. Scope - Exercise @sigilry/dapp, @sigilry/react, and @sigilry/cli together. - Provide a reproducible local flow for: - provider discovery (the demo wallet announces over canton:announcePr

@sigilry/canton-json-api Generated TypeScript types and Zod schemas for Canton JSON API v2, usable with the CIP-0103 ledgerApi method. What this package provides - TypeScript types generated from the pinned Canton OpenAPI spec - Zod schemas generated from the same OpenAPI source - int64 fie

@sigilry/canton-json-api Spec Overview @sigilry/canton-json-api provides generated TypeScript types for Canton JSON API v2. Scope - Pin Canton release + SHA256 in scripts/version-config.json. - Fetch and verify Canton release tarball. - Extract and check in api-specs/openapi.yaml from

@sigilry/cli TypeScript code generation from DAML DARs for Canton Network applications, including applications using Sigilry's CIP-0103 dApp SDK. Install yarn add --dev @sigilry/cli@^0.3 The CLI has its own 0.x version line. Wallet connectivity uses @sigilry/dapp@^3 and, for React

@sigilry/cli Spec Overview @sigilry/cli generates TypeScript from DARs and provides project setup helpers for Sigilry consumers. Scope - CLI entrypoint (sigilry) with codegen workflow support. - Config loading and resolution (sigilry.config.*). - Reliable invocation of dpm and clea

Provider Discovery & Push-Event Channel — @sigilry/dapp Spec Supporting spec for ./SPEC.md. Covers the two capabilities @sigilry/dapp is missing to be a complete, announce-first Canton dApp toolkit: provider discovery (the canton:announceProvider tier) and the **push-event

@sigilry/dapp Core package for CIP-103-compliant dApp ↔ wallet extension communication on Canton Network. Provides the typed SpliceProvider interface, JSON-RPC client/server, transports, and Zod schemas generated from th