Commit History
-
[NOTICKET] docs(knowledge): MinerU is dropped, not demoted — sync every status claim
Rifqi Hafizuddin +1: Claude Opus 5The docs described MinerU as "the fallback" (written 2026-09-02, before the 2026-09-07 decision to drop it) while `26ba1ab` had already commented it out of the extra and left it installed nowhere. Nine live status claims across eight files said otherwise. Docs only. Canonical wording now used everywhere: MinerU was DROPPED 2026-09-07 — commented out of the knowledge-parsing extra and installed nowhere, not the Space and not the dev venv (verified). It is NOT a fallback; there is one parser, Mistral OCR. Its code paths in src/knowledge_parsing/ are untouched (comment-out-don't-delete) and every MinerU measurement stays as record. REPO_STATUS 14 banner rewritten; the deps paragraph replaced - it described `uv sync --extra knowledge-parsing` as broken and told the reader to `uv pip install mineru` by hand, both now wrong. The `--no-sync` note keeps the convention but records that its…6281877 -
[NOTICKET] docs(knowledge): reframe as a Product-B experiment; persistence contract v2
Rifqi Hafizuddin +1: Claude Opus 5Records the 2026-09-07 discussion with Rifqi and a read-only introspection of the live dedorch database. Docs only - no code, no DDL executed. WHAT THE PIPELINE IS FOR. The review loop, the admin ingestion role and the curated-artifact lifecycle belong to a SEPARATE B2B knowledge product, where a company admin configures the company's knowledge and an expert reviews candidates before that company's normal users consume them. This repo is where the concept is tested cheaply on real documents. Data Eyond's own version is one added step: a user clicks a button and knowledge is extracted from ALL that user's documents in one batch - no admin role, no curation UI. Context doc gains 1.5 (two products) and 1.6 (multi-document semantics). MULTI-DOCUMENT SEMANTICS SETTLED. Entries append, never merge; entity_id stays document-scoped; cross-document overlap is CLASSIFIED (new/duplicate/ conflicting) and surfaced, never silently collapsed; DomainContext stays per document because purpose_verbat…0c20b40
-
[NOTICKET] docs(knowledge): reflect Mistral OCR as the primary parser
Additive documentation refresh — MinerU content is kept as the fallback's record, current state added alongside it. - KNOWLEDGE_PARSING_OUTPUT_CONTRACT: current-state callout; schema 0.3.0 -> 0.3.3 with source_title / normaliser_version / page_no added to the field tables. - knowledge_parsing/README: Mistral is the default backend (no GPU, MISTRAL_API_KEY); mistral_ocr.py + normalize_mistral.py listed; MinerU backends marked as fallback. - eval/parsing/README: Mistral rows added (section 0.878 / page 0.951), beating MinerU at both granularities; chunking stays section. - KNOWLEDGE_PARSING_COST: flagged as the MinerU (fallback) cost analysis; primary is Mistral (~$40/20k pages, no GPU). - KNOWLEDGE_PIPELINE_CALIBRATION: parsing sections now describe the fallback; extraction constants unchanged. - KNOWLEDGE_PIPELINE_TODO: S6b closed (page_no), B7 done (Mistral = second parser behind the identical artifact). - context / DEV_PLAN / REPO_STATUS: parser labelled Mistral (MinerU …854d373 -
[NOTICKET] docs(knowledge): v3 delta in the workstream docs
Rifqi Hafizuddin +1: Claude Opus 5Completes the doc sync for `172d8dc`, alongside `6a9fb78`. - TODO: new X26 for the v3 reshape; X24 annotated as superseded for the domain branch. Numbered X26 rather than X25 because X25 ("baselines expire") already exists - task ids are cited from other docs and must not be reused. - CALIBRATION: the guarded-field table read `summary | (none - generation cannot be span-checked at all)`. That was a principle, not just a fact, and a future change would reasonably have built on it. It now reads `title, purpose_verbatim`, with the reason the exception disappeared: the branch was asked to LOCATE rather than SUMMARISE, so there is something to check against. - CONTEXT: the review-stage mermaid node "Brief Context" -> "Domain Context", and the per-branch model-tier principle amended - Summary was classed with Rule as reasoning/generation needing a larger tier "because a plausible summary cannot be span-checked". That premise no longer holds. This closes the X26 referenc…58e2002
-
[NOTICKET] docs: reorganise into docs/ and give every doc a status banner
Rifqi Hafizuddin +1: Claude Opus 5The root carried 14 markdown files and no way to tell which were authoritative. That knowledge lived in CLAUDE.md §1 and in Rifqi's head, which works for us and fails for anyone else — and one of the stale ones already has a named failure mode ("The Stale-Doc Believer") for being implemented from. Root now holds four: REPO_STATUS, DEV_PLAN, API_CONTRACT_BE_PYTHON, README. Everything else moves under docs/, by git mv so history follows: docs/knowledge/ context, TODO, calibration, parsing output contract docs/plans/ SPINE_V2_PLAN (approved, W3 deferred), DS_TOOLS_PLAN (proposal) docs/archive/ API_ENDPOINTS_RESTRUCTURE, CODE_REVIEW_2026-07-23, PROJECT_BRD docs/reference/ API_CONTRACT_BE_GOLANG (the Go repo's, a copy that can drift) Every doc gains a one-line status banner under its H1, marked <!-- doc-status -->: LIVE / LIVE PLAN / PROPOSAL / ARCHIVED / REFERENCE. Archived ones name what superseded them — API_ENDPOINTS_RESTRUCTURE now opens with "DO NOT IMPLEMENT FROM…f1342ce