Foundgine

SES-900 — Foundgine Reference Implementation Profile (Informative)

SES-105 — Portable Semantic Execution Conformance Vectors · Standard Index · (end of family)


Status and purpose

Status: Draft 1.0 — Forward-looking specification and gap analysis.

This document is not a reverse-engineering report and is not a claim that the reference implementation already satisfies every requirement. It defines the target architecture for a production-grade, provider-neutral Semantic Execution System (SES), identifies the capabilities that remain to be specified or developed, and gives concrete acceptance criteria for future implementations.

The reference implementation may be used as an informative experiment, but the standard is the authority. Where the implementation and this specification differ, the implementation is considered incomplete until it is brought into conformance or the standard is deliberately amended.

Normative terms MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, and MAY have their usual standards meaning.

1. Purpose

Foundgine SHOULD be documented as a reference implementation profile, not as the source from which the standard is reverse engineered.

2. Relationship to the standard

The standard defines the target. Foundgine demonstrates selected design ideas and provides a concrete experimentation environment.

The mapping SHOULD therefore be maintained as:

SES requirement → Foundgine implementation candidate → Foundgine test evidence → known deviation

rather than:

Foundgine behavior → presumed standard requirement.

3. Required disclosure

The profile MUST identify features that are:

4. Strategic benefit

This separation allows Foundgine to evolve rapidly without forcing every experiment into the normative specification. It also makes it possible for other implementations to satisfy SES using different languages, providers, policy engines, and execution technologies.

5. Reference implementation matrix (2026-09-07 audit)

Built from src/ and src/csharp/tests/ in the Foundgine repository, following the §2 schema (SES requirement → Foundgine implementation candidate → Foundgine test evidence → status). A full machine-readable version, including a deviation field per row, is not published yet; the conformance/ directory currently holds requirements.json, known-gaps.json, and the conformance vectors. Status values follow §3: fully demonstrated, partially demonstrated, experimental, not implemented, provider-specific, not applicable.

SES Topic Implementation candidate Test evidence Status
SES-000 Terminology and conformance FoundgineOptions / FoundgineCapability (feature flags only) Not implemented
SES-001 Trust boundaries SecurityExecutionContext, ISecurityExecutionContextProvider AdversarialAgentBoundaryTests, Security.Tests/Penetration Partially demonstrated
SES-002 Canonical lifecycle FoundgineEngine, IFoundgine AuthorizationGoldenPathTests, ArchitectureBoundaryTests Partially demonstrated
SES-003 Semantic contract ISemanticContractProvider, SemanticContractSnapshot, SemanticContractAttestation SemanticContractProviderTests, SemanticContractAttestationTests, SemanticContractRuntimeBoundaryTests Fully demonstrated
SES-004 Operation graph SemanticOperationGraph, SemanticOperationGraphSafetyValidator SemanticOperationGraphStep30Tests, SemanticOperationGraphSafetyStep32Tests Fully demonstrated
SES-005 Operation algebra SemanticOperationAlgebra SemanticAlgebraTests, ExecutionAlgebraInvariantTests Fully demonstrated
SES-006 Retrieval and resolution EntityResolver, SemanticLexicalResolver, pgvector/Elasticsearch candidate sources SemanticRequestResolverTests, SemanticApproximateRetrievalTests, Postgres.Vector.Tests Fully demonstrated
SES-007 Logical traversal SemanticTraversal OpenIntentTraversalTests, NestedCollectionTraversalTests Partially demonstrated
SES-008 Authorization model SemanticAuthorizer, ISemanticAuthorizationPolicy SemanticAuthorizationTests, AuthorizationGoldenPathTests, AuthorizationInvariantTests Fully demonstrated
SES-009 Authorization provenance SemanticPlanAuthorizationBinding, SecurityWarrant* AuthorizationPreservationProofTests, Security.Authority.Tests provenance/integrity suite Fully demonstrated
SES-010 Planning and rewrites Planner, IPlanRewriteRule, RewriteRuleComposer PlannerTests, PlanOptimizationProofTests, RewriteRuleCompositionTests Fully demonstrated
SES-011 Execution IR ExecutionIR, ExecutionIRBoundary ExecutionIRTests, ExecutionBoundaryTests Fully demonstrated
SES-012 Provider boundary IExecutionProvider, SqlExecutionProvider, InMemoryProvider ProviderExecutableConformanceGateTests, ProviderSecurityConformanceMatrixTests Provider-specific (SQL/Postgres + in-memory only)
SES-013 Mutations SemanticMutationBuilder, MutationPlanner, PostgresBatchedMutationExecutionProvider ComplexSemanticMutationE2ETests, TransferFundsTests, Postgres transfer-funds suite Fully demonstrated
SES-014 Plan caching IProviderPlanCache, MemoryProviderPlanCache PlanCacheTests, ContextSafePlanCacheTests, SecurityPlanCachePartitionTests Partially demonstrated (in-memory only)
SES-015 Transports and agents FoundgineMcpTools, HotChocolateSemanticAdapter MCP.Tests (8 files), GraphQL.HotChocolate.Tests (26 files), MultiProducerEquivalenceTests Provider-specific (MCP + GraphQL only)
SES-016 Resource governance SecurityResourceLimits, MutationSecurityResourceLimitValidator SecurityResourceLimitTests, ResourceExhaustionPenetrationTests Partially demonstrated
SES-017 Evidence and observability ExecutionEvidence, ExecutionReceipt, IAuditLog EvidenceTests, ExecutionReceiptUnificationTests Partially demonstrated
SES-018 AOT and generated metadata GeneratedSemanticField, FoundgineMetadataGenerator Foundgine.Aot.Tests (all 3 files) Fully demonstrated
SES-019 Future development roadmap — (backlog document) Not applicable
SES-020 Formal data model — (C# POCOs only, no schema artifact) Not implemented
SES-021 State machines SecurityWarrantDelegationStateMachine, SecurityWarrantTrustTransition SecurityWarrantDelegationStateMachineSecurityTests, SecurityWarrantTrustTransitionSecurityTests Partially demonstrated (security-warrant only; no lifecycle-level state machine)
SES-022 Wire protocol JsonReadIntentAdapter (transport-specific only) JsonReadIntentAdapterTests Not implemented
SES-023 Versioning and compatibility SemanticVersion, SemanticModelFingerprint SemanticModelFingerprintTests Experimental
SES-024 Authority and delegation SecurityWarrantDelegationChain, SecurityWarrantDelegationCompromise/Concurrency Warrant delegation chain/compromise/concurrency security tests, WarrantTrustBoundaryPenetrationTests Fully demonstrated
SES-025 Provider capability profiles SemanticCapabilityContract, AggregateProviderCapability AggregateProviderCapabilityTests, ProviderSecurityConformanceMatrixTests Partially demonstrated (SQL/Postgres only)
SES-026 Proof and attestation AggregateRewriteProof, AuthorizationPreservationProof, SecurityInvariantProof, SemanticContractAttestation Matching *ProofTests/*AttestationTests across Semantics.Tests and Planning.Tests Fully demonstrated
SES-100 Conformance testing scripts/verify-conformance.py 246 xUnit tests across 13 projects (informative only) Partially demonstrated
SES-101 Test architecture, fixtures, oracles — (no ‘oracle’/’differential’ concept anywhere in the codebase) Not implemented
SES-102 Conformance matrix conformance/requirements.json, conformance/known-gaps.json Partially demonstrated (seed registry only, not full traceability)
SES-103 Security conformance Security.Tests/Penetration (11 files), Security.Authority.Tests (17 files) Partially demonstrated
SES-104 Future implementation gap matrix conformance/known-gaps.json Fully demonstrated
SES-105 Portable conformance vectors — (src/csharp/benchmarks/ directories are performance benchmarks, not conformance vectors) Not implemented

Cross-cutting notes:


SES-105 — Portable Semantic Execution Conformance Vectors · Standard Index · (end of family)