Claude CodeandClaude Opus 5 a1b3fef1ac
CI (SIAX Cloud) / sonar (push) Skipped
CI (SIAX Cloud) / security (push) Successful in 16s
CI (SIAX Cloud) / contracts (push) Successful in 31s
Component conformance / Component conformance (blocking) (push) Failing after 45s
CI (SIAX Cloud) / quality (push) Successful in 1m53s
CI (SIAX Cloud) / sonar (pull_request) Skipped
CI (SIAX Cloud) / security (pull_request) Successful in 35s
security / scan (pull_request) Failing after 26s
Component conformance / Component conformance (blocking) (pull_request) Failing after 46s
CI (SIAX Cloud) / contracts (pull_request) Successful in 50s
CI (SIAX Cloud) / quality (pull_request) Successful in 2m15s
fix(web): byt ut platshallarsidan mot en riktig C0PY-konsol
c0py.siax.io och c0py-web.siax.io renderade bokstavligen <div>c0py</div>
(4 tecken synlig text) - rotsidan var en platshallare i repot, inte ett
driftfel. Headless-matning 2026-11-11 fran server11: HTTP 200, tom title,
textLen=4, 0 lankar, 0 knappar.

Rotsidan renderar nu riktigt innehall grundat i repots egna fakta:

* produktidentitet och syfte ur README.md,
* LIVE API-status last server-side ur API:ets egen publika /health
  (status, CL0UD-bindning, API-tid, lastid) - och en uttrycklig
  "kunde inte lasas"-text nar API:et inte svarar, aldrig en pahittad status,
* den faktiska API-ytan (/health publik, /v1/c0py/registries|scans bearer)
  enligt apps/api/src,
* den kanoniska pipelinen ur README/MASTERPLAN.

Dessutom:
* /api/health for c0py-web (status, commit, apiBaseUrl) - samma monster som
  ovriga SIAX-produkter; Dockerfile.web skriver commit till /app/.c0py-commit
  och HEALTHCHECK pekar nu pa /api/health i stallet for /,
* app/icon.svg - c0py-surfacen gav 404 pa /favicon.ico vid varje sidladdning,
* 7 enhetstester for statuslasningen (inkl. att fel och timeout INTE
  rapporteras som ok) ersatter noop-testet.

SIAX-design: Inter, blacksvart rubrik #15151B, violett sidkant #5326CC,
morkt identitetsfalt. Inga nya beroenden (lockfilen oforandrad), inga lokala
DES1GN-primitivnamn exporteras.

Verifierat lokalt: validate:architecture OK, typecheck OK, 7/7 webbtester,
next build OK, next start ger 1475 tecken synlig text och /api/health 200
med live API-status (HTTP 200, status ok, cl0ud disabled).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-11 01:10:48 +01: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
346 KiB
Languages
TypeScript 97.2%
JavaScript 1.6%
Dockerfile 1.2%