docs: fix 6→8 modalities drift (add Provenance + Spatial)

deployment-modes.adoc and federation-readiness.adoc both described
the octad as six modalities. Authoritative sources (CLAUDE.md, the
TeX data model, rust-core/ crate layout) have eight — Provenance and
Spatial were added but docs never caught up.

Also adds the two missing normalizer regeneration strategies
(Provenance hash-chain reconstruction, Spatial coord re-extraction).

Foldback from verisim-modular-experiment Phase 0 archaeology.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

docs/VQL-SPEC.adoc docs/VCL-SPEC.adocdocs/VQL-SPEC.adoc renamed to docs/VCL-SPEC.adoc

@@ -8,7 +8,7 @@ VeriSimDB is **both** a database and a federation coordinator—the architecture
 
 === Mode 1: Standalone Database (Traditional)
 
-Deploy VeriSimDB as a **complete database system** with all six modalities local.
+Deploy VeriSimDB as a **complete database system** with all eight modalities local.
 
 [cols="1,3"]
 |===
@@ -18,7 +18,7 @@ Deploy VeriSimDB as a **complete database system** with all six modalities local
 |Local in-memory namespace
 
 |Modality Stores
-|All 6 modalities running on the same machine/cluster
+|All 8 modalities running on the same machine/cluster (Graph, Vector, Tensor, Semantic, Document, Temporal, Provenance, Spatial)
 
 |Use Case
 |Single institution, traditional database replacement

docs/deployment-modes.adoc

@@ -8,7 +8,7 @@
 
 == What Federation Means in VeriSimDB
 
-Federation is the ability for multiple VeriSimDB instances to coordinate queries across their respective octad stores. Each instance maintains its own six modality stores (Graph, Vector, Tensor, Semantic, Document, Temporal) and its own set of octad entities. A federated query spans multiple instances, retrieving and correlating data from peers that may be geographically distributed, operated by different organizations, or running different versions of VeriSimDB.
+Federation is the ability for multiple VeriSimDB instances to coordinate queries across their respective octad stores. Each instance maintains its own eight modality stores (Graph, Vector, Tensor, Semantic, Document, Temporal, Provenance, Spatial) and its own set of octad entities. A federated query spans multiple instances, retrieving and correlating data from peers that may be geographically distributed, operated by different organizations, or running different versions of VeriSimDB.
 
 Federation in VeriSimDB is distinct from database replication. Replicated databases maintain identical copies of the same data. Federated VeriSimDB instances hold _different_ octad entities that may reference each other through graph edges, share semantic vocabularies, or have vector embeddings in the same latent space. The federation layer coordinates cross-instance queries while each instance retains sovereignty over its own data.
 
@@ -60,14 +60,16 @@ If VCL were removed or not used, VeriSimDB would lose the following federation-c
 
 === Normalizer Regeneration Strategies Are Stubs
 
-The `verisim-normalizer` crate's regeneration strategies currently return hardcoded `[regenerated]` placeholder values. When drift is detected and normalization is triggered, the normalizer identifies the authoritative modality and calls the appropriate regeneration strategy, but that strategy does not actually regenerate the drifted modality's data. Each of the six modalities needs a real regeneration implementation:
+The `verisim-normalizer` crate's regeneration strategies currently return hardcoded `[regenerated]` placeholder values. When drift is detected and normalization is triggered, the normalizer identifies the authoritative modality and calls the appropriate regeneration strategy, but that strategy does not actually regenerate the drifted modality's data. Each of the eight modalities needs a real regeneration implementation:
 
 * **Graph**: Re-derive edges from document content and semantic annotations.
 * **Vector**: Re-embed from document text using the configured embedding model.
 * **Tensor**: Re-compute tensor representation from source data.
 * **Semantic**: Re-extract type annotations and RDF triples from document and graph.
 * **Document**: Re-generate searchable text from graph, semantic, and temporal data.
 * **Temporal**: Re-build version chain from modification history.
+* **Provenance**: Re-construct SHA-256 hash chain from temporal modification history and recorded actor trail.
+* **Spatial**: Re-extract geographic coordinates from document (via NER) and graph geographic references.
 
 === Federation Executor Always Returns Empty