3 Commits

Include renames

Author	SHA1	Message	Date
Claude Opus 5	4bc79c25d3	docs: withdraw the "Superset / OpenMetadata are OUT" rows — both are canonical ... `docs/02-architecture.md` was written when 0pt was planned as a standalone SaaS product. Its "Stack decisions — OUT (do not add)" table rejects Apache Superset ("Metabase already covers BI") and DataHub/OpenMetadata ("enterprise-heavy"), and the "IN" table names Metabase as the BI choice. Under the SIAX Cloud analytics decision, 0pt is the canonical Analytics/Data/Semantic owner — there is no BI0/Analytics0 repo and no separate Superset platform. Superset is the canonical BI engine (Apache-2.0, official embed SDK + guest tokens) and OpenMetadata the canonical catalog, default ahead of DataHub. Metabase, DataHub, Lightdash, Rill and Grafana are optional App Catalog apps, never the platform default. This repository had already shipped both of the "rejected" tools, which is what makes the old rows self-contradicting rather than merely stale: * src/metadata/openmetadata-adapter.ts + tests/contracts/metadata-features.contract.test.ts (STATUS.md classifies the OpenMetadata projection IMPLEMENTED) * services/infra/docker-compose.data-stack.yml defines a `superset` service (apache/superset:latest), and docs/compliance/OSS-INVENTORY.md line 74 already inventories `superset | Apache-2.0 | services/infra/data-stack` Falsifiable check used (asserts the OUT table no longer rejects either tool and that the IN table's BI row names Superset): origin/main -> FAIL (4 findings) this branch -> PASS mutation: BI row back to Metabase -> FAIL mutation: OUT rows un-struck -> FAIL Docs only. No workflow files, no .gitignore, no source. `node scripts/siax-doctor.mjs` gives 39/40 on this branch and 39/40 on main — the one failure (P1-15 CODEOWNERS missing) is pre-existing and is what PR #19 supplies. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-06 09:46:35 +02:00
adminandClaude Sonnet 5	2902a26bac	docs: full accuracy overhaul, grounded claim-by-claim in real code (#4) ... * docs: full accuracy overhaul, grounded claim-by-claim in real code Every doc in this repo (CLAUDE.md, README.md, SECURITY.md, docs/*.md) was audited and rewritten by a multi-pass process: independent rewrite per cluster, adversarial re-verification of that rewrite against the actual code, then a final cross-doc consistency pass — each stage re-checking claims against the repo directly rather than trusting the previous stage. Two corrections matter most: 1. docs/ICEBERG_WRITE_BOUNDARY.md, docs/11-lakehouse-write-plan.md, and docs/P0_QUERY_SOURCE_FLOW.md asserted src/services/quality-check-service.ts, quality-report-service.ts, src/data-platform/services/catalog-service.ts, and sql/002_p0_dataset_quality.sql/sql/003_*.sql as real, tested code. git log --all across every branch shows zero commits for any of these paths, ever. 0pt's data-quality/QA enforcement does not exist in code. Corrected everywhere, with a new docs/P0_DATASET_QUALITY_FLOW.md added as an explicit target-spec (not-yet-built) replacement. 2. github.com/sax3l/0pt (this repo) and git.siax.io/sax3l/0pt (Gitea) are two diverged remotes sharing part of the same history (services/api/ workers/adaptive_router.py is byte-identical between them). Gitea's main independently accumulated a WAF-bypass/proxy-rotation scraper stack in three 2026-07-13 commits, since removed via a Gitea PR; GitHub's main never had it. Which remote is canonical/deployed is unresolved — flagged consistently across the corpus, not decided here. Also newly and consistently documented: the tenant_id/project_id-read-from- client-body gap on the P0 lakehouse/rate-policy/source-query routes (no auth/session system exists anywhere in this repo yet); that every CL0UD/ N0D/AUD0/ST0RE platform client is real but mock-only (zero process.env reads for any of their *_URL vars); that two P0 mutation routes (lakehouse/mappings, sources/rate-policies) always fail over HTTP today because their prerequisite entity can never be created via any route; a schema bug in sql/004 (FK references to opt_datasets/opt_sources, which don't exist); and that 0pt.app's live deployment was independently confirmed (curled this pass) to be running this exact codebase with DATABASE_URL/REDIS_URL unset in production. New file: docs/12-edge-capability-api.md — the edge-native P0 TypeScript capability contract (app/api/0pt/*, /api/screen, /api/ai/parse), previously undocumented and distinct from docs/04-api.md's FastAPI-engine-only scope. Verified before commit: tsc --noEmit clean; vitest run 88 passed, 1 todo, 0 failures (13 files) — docs-only change, no source touched. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * docs: reflect PR #5's lakehouse-mapping-registry + status-code fixes Follow-up to keep docs/12-edge-capability-api.md accurate once both PRs land: fix/0pt-full-bug-hunt (#5) fixed the shared-instance bug in the lakehouse mapping routes and added proper status-code mapping to the document extraction route. This doc was written against the pre-fix state in the same pass that added it, so it needs the same correction. Does not claim the lakehouse write path fully works now -- the deeper dataset-registration gap (no route ever calls DatasetService.registerDataset) is unchanged and still blocks it end-to-end; only the shared-instance half of the bug is fixed. --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-22 18:49:01 +02:00
adminandClaude Opus 4.8	22e09d984d	feat: rebrand MONO->0pt (hero, header, layout) + add project docs/contract ... Hero is now a data-native 0pt artifact (no photos, keeps grain/reveal/float); header is the 0pt wordmark with Swedish nav; layout is sv + loads JetBrains Mono + 0pt metadata; globals wires the loaded fonts. Adds CLAUDE.md + docs/01-09 as the build contract. next build green (5 routes). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-24 17:38:07 +02:00