Updated README.md

.filenesting.json

@@ -0,0 +1,3 @@
+{
+    "help":"https://go.microsoft.com/fwlink/?linkid=866610"
+}

CONTRIBUTING.md

@@ -35,7 +35,7 @@ Open a GitHub Issue with:
 ### Pull Requests
 
 - Target the `main` branch.
-- All tests must pass: `dotnet test Svrn7.sln`
+- All tests must pass locally: `dotnet test Web7-DSA.sln`
 - New behaviour requires new tests.
 - C# code must target .NET 8 (`net8.0`), use nullable reference types, and follow the
   existing naming conventions (see `README.md` Section 19).

docs/SVRN7_Comprehensive_Prompt.md

@@ -100,7 +100,7 @@ teams, poker parties, tribes, clans, political parties, and any other form of di
 **10 projects (8 src, 2 test). 25 C# files. ~7,427 lines. Zero stubs. Zero TODOs.**
 
 ```
-Svrn7.sln
+Web7-DSA.sln
 ├── src/
 │   ├── Svrn7.Core/        — Models, interfaces, exceptions, constants. Zero deps.
 │   ├── Svrn7.Crypto/      — secp256k1, Ed25519, AES-256-GCM, Blake3, Base58btc
@@ -693,3 +693,18 @@ Formally defined in draft-herman-parchment-programming-00 Section 5.2.1.
 ### Conditional Components Criteria examples:
 - "Society TDA Only"  → Schema Registry, DID Doc Registry, VC Doc Registry (and their resolvers)
 - "Epoch 1+"          → components activated at epoch transition
+
+## PPML Core Principles (PP-1 through PP-9)
+
+PP-1: Diagram Primacy — diagram is the source of truth; code conforms to diagram.
+PP-2: Legend Formalism — every element type formally defined in the Legend.
+PP-3: Element Instance Unambiguity — every element belongs to exactly one type.
+PP-4: Tractability — every element has an artefact or Gap Register entry.
+PP-5: Change Record — diagram changes precede code changes.
+PP-6: Epoch Stability — Legend frozen within an epoch.
+PP-7: AI Legibility — diagram sufficient for correct AI code generation.
+PP-8: Living Specification — diagram evolves with the system across its lifetime.
+PP-9: Consistent Code Generation — two independent generators given the same conformant
+      diagram MUST produce functionally equivalent artefacts (same interfaces, ownership,
+      dependencies, protocol registrations). Enables session independence: the diagram
+      alone is sufficient to regenerate any artefact without chat history or prior context.

docs/llms.txt

@@ -397,3 +397,18 @@ Elements 7, 8, 10 are Web 7.0 / SVRN7 specific (substitute equivalents for other
 
 Each LOBE ships .psm1 + .psd1 + .lobe.json (MCP-aligned descriptor).
 lobes.config.json: eager = [Common, Federation, Society, UX]; jit = [Email, Calendar, Presence, Notifications, Onboarding, Invoicing, Identity]
+
+## PPML Core Principles (PP-1 through PP-9)
+
+PP-1: Diagram Primacy — diagram is the source of truth; code conforms to diagram.
+PP-2: Legend Formalism — every element type formally defined in the Legend.
+PP-3: Element Instance Unambiguity — every element belongs to exactly one type.
+PP-4: Tractability — every element has an artefact or Gap Register entry.
+PP-5: Change Record — diagram changes precede code changes.
+PP-6: Epoch Stability — Legend frozen within an epoch.
+PP-7: AI Legibility — diagram sufficient for correct AI code generation.
+PP-8: Living Specification — diagram evolves with the system across its lifetime.
+PP-9: Consistent Code Generation — two independent generators given the same conformant
+      diagram MUST produce functionally equivalent artefacts (same interfaces, ownership,
+      dependencies, protocol registrations). Enables session independence: the diagram
+      alone is sufficient to regenerate any artefact without chat history or prior context.