ttl-policy

ekson73's avatarfrom ekson73

Manage Time-To-Live policies for framework content freshness

⭐0stars🔀1forks📁View on GitHub🕐Updated Jan 10, 2026⬇️2downloads
[Knowledge Base]

When & Why to Use This Skill

This Claude skill provides a comprehensive system for managing Time-To-Live (TTL) policies to maintain content freshness within multi-agent frameworks. It automates the monitoring of document expiration, tracks provenance through standardized PROV tags, and enforces synchronization protocols to ensure that agents always operate with the most accurate and up-to-date information.

Use Cases

  • Automated Content Freshness Monitoring: Automatically track the expiration of technical documents, protocols, and reference data, ensuring agents never use stale or outdated information.
  • Standardized Provenance Tracking: Implement consistent PROV tags (Markdown, HTML, or JSON) to maintain a clear audit trail of content sources, versions, and sync dates.
  • Lifecycle Management for Technical Docs: Define specific TTL intervals for different content types, such as 14 days for roadmaps and 90 days for core protocols, to trigger timely reviews.
  • Upstream Data Synchronization: Streamline the process of pulling updates from GitHub or other repositories when content is flagged as expired, maintaining a reliable knowledge base.
namettl-policy
descriptionManage Time-To-Live policies for framework content freshness
version1.0.0

TTL Policy Skill

Purpose

Manage Time-To-Live (TTL) policies for content consumed from the multi-agent-os framework. Ensures information freshness and triggers review cycles when content expires.

When to Use

  • When consuming content from framework
  • When checking document freshness
  • When syncing from upstream
  • When reviewing stale content

TTL by Content Type

Type TTL (days) Rationale
Protocol/Standard 90 Core protocols are stable
API Documentation 60 Interfaces change moderately
Configuration 30 Configs need frequent updates
Roadmap/Timeline 14 Time-sensitive
Security Policy 90 Security requires stability
Decision Record 180 Decisions are long-lived
Tutorial/Guide 60 Examples may need updates
Reference Data 30 Data freshness matters

Status States

🟢 FRESH    → now < expires - 7d    → Use normally
🟡 EXPIRING → expires-7d < now < expires → Alert, plan review
🔴 EXPIRED  → now >= expires        → Block usage, require refresh

PROV Tag Format

Add provenance tracking to consumed content:

Compact (1-line)

<!-- PROV: https://github.com/ekson73/multi-agent-os/blob/main/protocols/hmp.md | v1.0 | sync:2026-01-07 | TTL:90d | exp:2026-04-07 -->

Inline (Markdown-safe)

[//]: # (PROV: https://github.com/ekson73/multi-agent-os/blob/main/protocols/hmp.md|v1.0|2026-01-07|TTL90|exp:2026-04-07)

JSON

{
  "_prov": "https://github.com/ekson73/multi-agent-os/blob/main/protocols/hmp.md|v1.0|2026-01-07|TTL90|exp:2026-04-07"
}

PROV Fields

Field Format Example
full-url GitHub URL https://github.com/.../file.md
version Semver v1.0
sync ISO date sync:2026-01-07
TTL Days TTL:90d
exp ISO date exp:2026-04-07

Agent Actions by Status

Status Agent Action Human Action
🟢 FRESH Use normally None needed
🟡 EXPIRING Warn human Schedule review
🔴 EXPIRED Block, require refresh Sync from upstream

Sync Protocol

When content is EXPIRED:

  1. Check upstream for updates
  2. Pull latest version
  3. Update sync date
  4. Recalculate expiration
  5. Update PROV tag

Skill based on TTL Policy v1.0 | multi-agent-os