Answers are grounded in this paper and cite their sources.
Technical specification demonstrates a portable file-grammar for context-dependent digital artefacts, highlighting verifiable lifecycle states governed by temporal and spatial rules.
Situated Living Files (SLF) v0.1 specifies a portable file-grammar form for declaring, exhibiting, and verifying situated digital acts as digital artefacts. An SLF artefact is a digital artefact whose validity, use, consumption, expiration, rejection, revocation, failure, and verifiable residue depend on declared temporal, spatial, and contextual conditions. This package includes the populated SLF v0.1 specification body (§0–§19), standalone JSON Schemas, and standalone JSON examples. The specification covers ordinary SLF artefacts, declared temporal/spatial/contextual conditions, lifecycle states and transitions, evaluation context, verifiable residues, detached proof references, JSON grammar, conformance, security/privacy considerations, and publication/verification notes. This package uses a dual licensing structure: prose specification and documentation files are licensed under Creative Commons Attribution 4.0 International (CC BY 4.0 / CC-BY-4.0); machine-readable schemas, examples, and code-like artefacts are licensed under Apache License 2.0 (Apache-2.0). See publication/LICENSE for the per-file scope mapping. File-level SPDX-License-Identifier markers, when present, control for the marked file. Publication or verification of this package does not by itself establish legal validity, legal admissibility, regulatory compliance, truth certification, notarial substitution, tamper-proof security, blockchain replacement, evaluator trust-basis verification, mandatory proof-service validity, or global canonicality among divergent residues. Claim level (per the Volume II honest scale, 10.5281/zenodo.20744965): re-examinable, with a defined but empty detached-proof slot for third-party verification. No legal validity, certification or canonicality is claimed. This version adds a PDF rendering of the specification. The PDF is generated from the Markdown source included in the original package; the source file hash is recorded in the package manifest. The rendering introduces no changes to the normative content.
No takes yet. Share an insight, caveat, or question.
Francesco Riva (2026) studied this question.