Skip to content

Proposal: optional durability: durable | volatile frontmatter field for GC/compaction hints #172

Description

@chirag127

Proposal

Optional frontmatter field durability: durable | volatile.

Meaning

  • durable — concept should persist across bundle cleanups. Fundamental facts, standing decisions, invariants.
  • volatile — concept is time-boxed; safe to prune during garbage collection or context compaction. Session summaries, migration notes, in-flight state.
  • absent — no assertion; consumers treat as durable by default (backward-compatible).

Why not covered by existing fields

Concrete gap

An agent doing context compaction over a bundle needs to answer: "if I evict this concept, do I lose institutional knowledge or ephemeral state?" Currently the only signal is guessing from type / path / age.

Adopter data

828 concept files at chirag127/workspace/knowledge/ ship this field optionally as of 2026-07-03. Public bundle: knowledge.oriz.in.

Proposed SPEC.md addition (§4.1 Frontmatter, Extensions block)

durability: durable | volatile   # optional; controls GC/compaction eligibility. Absent = durable.

Backwards-compatible — no existing bundle breaks. Consumers ignoring the field keep prior behavior.

Not-in-scope

Thanks for the great work on OKF!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions