gf-01-langchain-pass
- Substrate
- langchain
- Claim Level
- Declared (Specimen)Exec: static / Inf: fake_llm
- Scenario
- gf-01-single-agent-lifecycle
- Ruleset
- ruleset-1.0(presence-level)
Third-Party Verification
Read-OnlyEvidence Status: Archived
This run does not have complete verification artifacts.
Future availability: Contact governance for evidence completion pathway.
📐 Mapping & Projection
governance/substrates/langchain/fingerprint.yamlgovernance/mappings/fieldmap/langgraph.yamlgovernance/mappings/normalization-spec.yamlgovernance/mappings/hash-scope.yamlgovernance/mappings/equivalence-criteria.yamlProjection-Only Disclaimer
Learn More →Mappings describe evidence projection only; they do not describe framework capability.
Evidence Pack
7 files- manifest
manifest.json - integrity
integrity/sha256sums.txt - integrity
integrity/pack.sha256 - timeline
timeline/events.ndjson - artifacts
artifacts/context.json - artifacts
artifacts/plan.json - artifacts
artifacts/trace.json
Governance & Scope
Source-Bound Reading
Read this run through the facts bound to the run itself: scenario ID, ruleset identity, admission/adjudication status, and the published evidence surfaces.
No Universal Spine
Legacy labels such as LG-*, gf-*, or older ruleset families may appear in run artifacts. They should be read only as identifiers carried by the bound evidence/adjudication data, not as a universal governance doctrine for every run.
Verdict Boundary
PASS, FAIL, NOT_EVALUATED, or NOT_ADMISSIBLE on this run mean only what the bound adjudication artifact says under its pinned ruleset. They do not by themselves imply protocol truth, certification, or broader capability claims.
No Execution Hosting
The Lab does NOT execute agent code. All evidence generation occurs in third-party environments.