YoVinchen 75592af33a Isolate cloud model access before enabling product RAG workflows ...

The API and ingestion tools now use a fixed internal model gateway while
governed profiles, embedding cache assignments, traceable citations, and
stable API errors establish the boundaries required by later workflows.

Constraint: The current Alibaba Cloud workspace rejects all three live model calls with authentication failures
Rejected: Give the API or seed tools the Bailian key and direct egress | combines database access, cloud credentials, and public network access
Rejected: Mix offline and Bailian vectors in one demo namespace | makes profile activation and retrieval ambiguous
Confidence: high
Scope-risk: moderate
Reversibility: clean
Directive: Keep Bailian credentials and egress exclusive to model-gateway and create a new immutable profile hash for any embedding identity change
Tested: make verify; 121 backend tests; 14 frontend tests; fresh and populated Alembic upgrade-downgrade-upgrade; two idempotent offline seeds; Docker health and HTTP retrieval; isolated provider smoke
Not-tested: Successful live Bailian responses because the supplied workspace credential currently fails authentication

2026-07-13 04:09:06 +08:00

..

bailian

Make the first RAG slice executable without risking production data

2026-07-12 15:41:58 +08:00

parsers

Establish a safe foundation before implementing the geology RAG system

2026-07-12 14:42:11 +08:00

fake.py

Make the first RAG slice executable without risking production data

2026-07-12 15:41:58 +08:00

model_gateway.py

Isolate cloud model access before enabling product RAG workflows

2026-07-13 04:09:06 +08:00