Tagged: Typed links
Typed links, edge metadata, and link syntax
Pages with this tag
Framework crosswalks
1How frameworks map to each other — specific crosswalk tables, column mapping strategies, and matching methods.
Link metadata syntax specification
2Complete specification of the typed-link syntax — wrapping styles, link types, regex patterns, and the two-tier priority system.
Link metadata system
3The theoretical foundation for typed links with edge metadata in Obsidian — how relationships between notes can carry structured data. Also known as edge metadata, typed link system, inline field metadata, or evidence-link edge model.
Challenge 07: Link metadata / edge model for evidence mapping (archived)
4Design the edge metadata model for evidence→framework implementation links — the "other" edge type Crosswalker has to support that's NOT a crosswalk. Bases-compatible storage, custom or inherited schema, reviewer attribution, status transitions. RESOLVED 2026-04-10, archived 2026-05-01.
Challenge 08: Is git history a tenable compliance audit trail?
5The 04-10 evidence-link synthesis assumed git history (with signed commits, branch protection, and periodic external snapshots) is a sufficient audit trail for evidence-link state changes. Stress-test that assumption against actual compliance audit-evidence standards, legal admissibility frameworks, and how mature GRC tools handle the same problem.
Challenge 13: Modern attestation primitives (Sigstore, in-toto, SLSA, OpenTimestamps, VCs)
6Narrower follow-on to Challenge 08. Evaluate the modern attestation stack — Sigstore for federated signing, in-toto for review attestations, SLSA for supply-chain framing, OpenTimestamps as alternative/complement to RFC 3161, W3C Verifiable Credentials for the qualified-person certification — and recommend whether these subsume, complement, or are skipped vs Challenge 08's TSA + WORM + cert-export Tier 1 plan.
Challenge 15: Audit-trail alternatives that don't require external git tooling (archived)
7Ch 08 + Ch 13 audit-trail stack assumes git + a remote (GitHub/GitLab/etc.) — a hard assumption in air-gapped, locked-down enterprise, or government environments. RESOLVED 2026-05-02 — see callout.
Evidence-link edge model synthesis — junction notes as the committed architecture
8Distilling 2 research sessions directly targeted at Challenge 07 (the link metadata / edge model for evidence mapping). Both converge strongly on junction notes (edge-as-note reification) as the only architecture compatible with Obsidian Bases' flat-YAML constraint, with a concrete 13-field schema validated against 8 GRC tools and OSCAL round-trip.
Foundation commitments and follow-on research — pairwise+pivot, junction-notes-by-tier, StewardshipProfile, meta-schema lifecycle
9Decisions made 2026-05-01 after re-reading the morning orientation log and the Challenge 06 research deliverable. Commits the pairwise + optional-pivot hybrid (Challenge 06 resolution); ties junction-note feasibility to tier; renames EvolutionPattern → StewardshipProfile; introduces the schema-marketplace direction; commits that every Crosswalker-internal schema is versioned and migration-aware (Crosswalker eats its own dog food); spins up three new research challenges (git-history audit-trail tenability, UUID/CWUUID strategy, graph→tabular bridging engine).
Ch 08 deliverable: Is git history a tenable compliance audit trail?
10Fresh-agent research deliverable for Challenge 08. Recommends augmenting bare git with three Tier 1 hardening layers: RFC 3161 trusted timestamps, S3 Object Lock WORM mirror, FRE 902(13) qualified-person certification export. Reaffirm git substrate; do not replace.
SKOS
11Simple Knowledge Organization System — the W3C mapping vocabulary that every modern crosswalk standard builds from, but that our research found insufficient for compliance crosswalking on its own.
SSSOM
12Simple Standard for Sharing Ontological Mappings — the edge metadata model that extends SKOS with mandatory provenance, confidence, and negation support.