admin f6ff1396d8
CI (SIAX Cloud) / contracts (pull_request) Successful in 17s
CI (SIAX Cloud) / contracts (push) Successful in 17s
CI (SIAX Cloud) / quality (pull_request) Successful in 54s
CI (SIAX Cloud) / quality (push) Successful in 56s
CI (SIAX Cloud) / security (pull_request) Successful in 1m7s
CI (SIAX Cloud) / security (push) Successful in 1m5s
feat(api): CL0UD capability probe + a11y/HAR evidence + worker scale toggle
- cl0ud client: contract-first probe of documented GET /capabilities/:id,
  status connected/denied/unavailable/disabled surfaced in /health;
  CL0UD_REQUIRED=true = fail-closed 503; full policy-decisions gated on
  CL0UD B-4/ADR-0031 (deliberately not simulated)
- capture depth: accessibility tree + condensed HAR as evidence kinds
  (null = explicit evidence gap)
- CAPTURE_WORKER=on/off for separate-scale deployments
- 34/34 tests
2026-09-16 23:21:54 +02:00

C0PY

Canonical SIAX engine for evidence-driven web product capture, digital-twin specification, reconstruction and verification.

C0PY consumes an authorized web target and produces a versioned Evidence Graph / Canonical IR covering routes, DOM/runtime state, styles, assets, responsive behavior, interactions, workflows, network contracts, motion, accessibility and product topology. Reconstruction builders consume frozen C0PY specs; they never become the source of truth.

Snabbkommandon

pnpm install
pnpm --filter @siax/c0py-api dev
pnpm --filter @siax/c0py-web dev

Canonical architecture

Source product
  -> discovery
  -> Playwright/CDP deterministic capture
  -> semantic workflow exploration adapters
  -> Evidence Graph / Canonical IR
  -> frozen reconstruction specs
  -> v0 / Lovable / Codex / generic builders
  -> preview deployment
  -> multidimensional QA
  -> typed repair loop

Repo structure

apps/api/          -> Fastify/API surface
apps/web/          -> Next.js console and visualisation
packages/c0py-core -> discovery, capture orchestration, evidence/provenance, product model, verification
packages/config    -> validated runtime configuration
packages/types     -> canonical shared IR/contracts
docs/spec/         -> full Digital Twin Specification
docs/MASTERPLAN.md -> canonical execution plan
docs/STANDARDS.md  -> mandatory engineering/evidence rules
docs/AUTOMATIONS.md -> autonomous pipeline contracts

Capability adoption

External technologies are classified as CORE, DEPENDENCY, CHERRY_PICK, ADAPTER, REIMPLEMENT, REFERENCE_ONLY or DROP. See docs/UPSTREAM-CAPABILITY-MATRIX.md.

Primary integrations include Playwright/CDP, Crawlee-compatible crawl orchestration, rrweb, Browser Use/Browser Harness adapters, deterministic pixel/style verification, optional Spector.js WebGL forensics, and isolated archival adapters. Builders include v0, Lovable, Codex and generic agents.

Operating modes

  • clone — maximize observed fidelity; synthetic facts are prohibited.
  • adapt — preserve approved semantics while transforming design/technology.
  • blend — combine explicitly selected capabilities/patterns with complete provenance.

Quality

C0PY does not use one visual score as a release verdict. It verifies a fidelity vector across geometry, typography, colors, assets, responsive states, routes, interactions, workflows, network contracts, motion, accessibility, runtime errors and production build health.

SIAX platform capabilities

Capability Purpose Status
CL0UD Authentication, RBAC, tenant live
AUD0 Audit/event delivery planned integration
ST0RE Evidence/object storage planned integration
INF0 AI/semantic analysis planned integration
N0D Async capture/reconstruction jobs planned integration

Deploy

SIAX Cloud via Coolify. Vercel is supported as a reconstruction preview adapter. See DEPLOY.md.

S
Description
Verktyg för att skapa fullständigt register över en hemsida ut alla aspekter
Readme MIT 326 KiB
Languages
TypeScript 96.8%
JavaScript 1.9%
Dockerfile 1.3%