decay

Name: decay
Author: NeoLabHQ

821installs132forks

How to install decay?

neolabhq/context-engineering-kit/decay

$npx -y skills add NeoLabHQ/context-engineering-kit --skill decay

Installs into the current project.

Summary

Manage evidence freshness by identifying stale decisions and providing governance actions

Files · 1

View on GitHub

SKILL.md

1	# Evidence Freshness Management
2
3	Manages evidence freshness by identifying stale decisions and providing governance actions. Implements FPF B.3.4 (Evidence Decay).
4
5	Key principle: Evidence is perishable. Decisions built on expired evidence carry hidden risk.
6
7	---
8
9	## Quick Concepts
10
11	### What is "stale" evidence?
12
13	Every piece of evidence has a `valid_until` date. A benchmark from 6 months ago may no longer reflect current system performance. A security audit from before a major dependency update doesn't account for new vulnerabilities.
14
15	When evidence expires, the decision it supports becomes questionable - not necessarily wrong, just unverified.
16
17	### What is "waiving"?
18
19	Waiving = "I know this evidence is stale, I accept the risk temporarily."
20
21	Use it when:
22	- You're about to launch and don't have time to re-run all tests
23	- The evidence is only slightly expired and probably still valid
24	- You have a scheduled date to refresh it properly
25
26	A waiver is NOT ignoring the problem - it's explicitly documenting that you know about the risk and accept it until a specific date.
27
28	### The Three Actions
29
30	\| Situation \| Action \| What it does \|
31	\|-----------\|--------\|--------------\|
32	\| Evidence is old but decision is still good \| Refresh \| Re-run the test, get fresh evidence \|
33	\| Decision is obsolete, needs rethinking \| Deprecate \| Downgrade hypothesis, restart evaluation \|
34	\| Accept risk temporarily \| Waive \| Record the risk acceptance with deadline \|
35
36	---
37
38	## Action (Run-Time)
39
40	### Step 1: Generate Freshness Report
41
42	1. List all evidence files in `.fpf/evidence/`
43	2. For each evidence file:
44	- Read `valid_until` from frontmatter
45	- Compare with current date
46	- Classify as FRESH, STALE, or EXPIRED
47
48	### Step 2: Present Report
49
50	```markdown
51	## Evidence Freshness Report
52
53	### EXPIRED (Requires Action)
54
55	\| Evidence \| Hypothesis \| Expired \| Days Overdue \|
56	\|----------\|------------\|---------\|--------------\|
57	\| ev-benchmark-2024-06-15 \| redis-caching \| 2024-12-15 \| 45 \|
58	\| ev-security-2024-07-01 \| auth-module \| 2025-01-01 \| 14 \|
59
60	### STALE (Warning)
61
62	\| Evidence \| Hypothesis \| Expires \| Days Left \|
63	\|----------\|------------\|---------\|-----------\|
64	\| ev-loadtest-2024-10-01 \| api-gateway \| 2025-01-20 \| 5 \|
65
66	### FRESH
67
68	\| Evidence \| Hypothesis \| Expires \|
69	\|----------\|------------\|---------\|
70	\| ev-unittest-2025-01-10 \| validation-lib \| 2025-07-10 \|
71
72	### WAIVED
73
74	\| Evidence \| Waived Until \| Rationale \|
75	\|----------\|--------------\|-----------\|
76	\| ev-perf-old \| 2025-02-01 \| Migration pending \|
77	```
78
79	### Step 3: Handle User Actions
80
81	Based on user response, perform one of:
82
83	#### Refresh
84
85	User: "Refresh the redis caching evidence"
86
87	1. Navigate to the hypothesis in `.fpf/knowledge/L2/`
88	2. Re-run validation to create fresh evidence
89
90	#### Deprecate
91
92	User: "Deprecate the auth module decision"
93
94	1. Move hypothesis from L2 to L1 (or L1 to L0)
95	2. Create deprecation record:
96
97	```markdown
98	# In .fpf/evidence/deprecate-auth-module-2025-01-15.md
99	---
100	id: deprecate-auth-module-2025-01-15
101	hypothesis_id: auth-module
102	action: deprecate
103	from_layer: L2
104	to_layer: L1
105	created: 2025-01-15T10:00:00Z
106	---
107
108	# Deprecation: auth-module
109
110	Reason: Evidence expired, technology landscape changed
111
112	Next Steps: Run `/fpf:propose-hypotheses` to explore alternatives
113	```
114
115	3. Move the hypothesis file:
116	```bash
117	mv .fpf/knowledge/L2/auth-module.md .fpf/knowledge/L1/auth-module.md
118	```
119
120	#### Waive
121
122	User: "Waive the benchmark until February"
123
124	1. Create waiver record:
125
126	```markdown
127	# In .fpf/evidence/waiver-benchmark-2025-01-15.md
128	---
129	id: waiver-benchmark-2025-01-15
130	evidence_id: ev-benchmark-2024-06-15
131	waived_until: 2025-02-01
132	created: 2025-01-15T10:00:00Z
133	---
134
135	# Waiver: ev-benchmark-2024-06-15
136
137	Evidence: ev-benchmark-2024-06-15
138	Hypothesis: redis-caching
139	Waived Until: 2025-02-01
140	Rationale: Migration pending, will re-run after completion
141
142	Accepted By: User
143	Created: 2025-01-15
144
145	WARNING: This evidence returns to EXPIRED status after 2025-02-01.
146	```
147
148	---
149
150	## Natural Language Usage
151
152	You don't need to memorize evidence IDs. Just describe what you want.
153
154	### Example Workflow
155
156	```
157	User: /fpf:decay
158
159	Agent shows report with stale evidence
160
161	User: Waive the benchmark until February, we'll re-run it after the migration.
162
163	Agent: Creating waiver for ev-benchmark-2024-06-15 until 2025-02-01.
164	Rationale: "Re-run after migration"
165
166	[Creates .fpf/evidence/waiver-benchmark-2025-01-15.md]
167
168	User: The vendor API is being discontinued. Deprecate that decision.
169
170	Agent: Deprecating hypothesis-vendor-api from L2 to L1.
171	[Moves file, creates deprecation record]
172
173	Next step: Run /fpf:propose-hypotheses to explore alternatives.
174	```
175
176	---
177
178	## WLNK Principle
179
180	A hypothesis is STALE if any of its evidence is expired (and not waived).
181
182	This is the Weakest Link (WLNK) principle: reliability = min(all evidence). One stale

People who liked this also viewed

6 picks

Type

lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026382k16k
lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026382k16k
lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026380k16k
lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026380k16k
lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026330k16k
lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026227k16k

decay

821installs132forks

View on GitHub

How to install decay?

neolabhq/context-engineering-kit/decay

$npx -y skills add NeoLabHQ/context-engineering-kit --skill decay

Installs into the current project.

Summary

Manage evidence freshness by identifying stale decisions and providing governance actions

Files · 1

View on GitHub

SKILL.md

1	# Evidence Freshness Management
2
3	Manages evidence freshness by identifying stale decisions and providing governance actions. Implements FPF B.3.4 (Evidence Decay).
4
5	Key principle: Evidence is perishable. Decisions built on expired evidence carry hidden risk.
6
7	---
8
9	## Quick Concepts
10
11	### What is "stale" evidence?
12
13	Every piece of evidence has a `valid_until` date. A benchmark from 6 months ago may no longer reflect current system performance. A security audit from before a major dependency update doesn't account for new vulnerabilities.
14
15	When evidence expires, the decision it supports becomes questionable - not necessarily wrong, just unverified.
16
17	### What is "waiving"?
18
19	Waiving = "I know this evidence is stale, I accept the risk temporarily."
20
21	Use it when:
22	- You're about to launch and don't have time to re-run all tests
23	- The evidence is only slightly expired and probably still valid
24	- You have a scheduled date to refresh it properly
25
26	A waiver is NOT ignoring the problem - it's explicitly documenting that you know about the risk and accept it until a specific date.
27
28	### The Three Actions
29
30	\| Situation \| Action \| What it does \|
31	\|-----------\|--------\|--------------\|
32	\| Evidence is old but decision is still good \| Refresh \| Re-run the test, get fresh evidence \|
33	\| Decision is obsolete, needs rethinking \| Deprecate \| Downgrade hypothesis, restart evaluation \|
34	\| Accept risk temporarily \| Waive \| Record the risk acceptance with deadline \|
35
36	---
37
38	## Action (Run-Time)
39
40	### Step 1: Generate Freshness Report
41
42	1. List all evidence files in `.fpf/evidence/`
43	2. For each evidence file:
44	- Read `valid_until` from frontmatter
45	- Compare with current date
46	- Classify as FRESH, STALE, or EXPIRED
47
48	### Step 2: Present Report
49
50	```markdown
51	## Evidence Freshness Report
52
53	### EXPIRED (Requires Action)
54
55	\| Evidence \| Hypothesis \| Expired \| Days Overdue \|
56	\|----------\|------------\|---------\|--------------\|
57	\| ev-benchmark-2024-06-15 \| redis-caching \| 2024-12-15 \| 45 \|
58	\| ev-security-2024-07-01 \| auth-module \| 2025-01-01 \| 14 \|
59
60	### STALE (Warning)
61
62	\| Evidence \| Hypothesis \| Expires \| Days Left \|
63	\|----------\|------------\|---------\|-----------\|
64	\| ev-loadtest-2024-10-01 \| api-gateway \| 2025-01-20 \| 5 \|
65
66	### FRESH
67
68	\| Evidence \| Hypothesis \| Expires \|
69	\|----------\|------------\|---------\|
70	\| ev-unittest-2025-01-10 \| validation-lib \| 2025-07-10 \|
71
72	### WAIVED
73
74	\| Evidence \| Waived Until \| Rationale \|
75	\|----------\|--------------\|-----------\|
76	\| ev-perf-old \| 2025-02-01 \| Migration pending \|
77	```
78
79	### Step 3: Handle User Actions
80
81	Based on user response, perform one of:
82
83	#### Refresh
84
85	User: "Refresh the redis caching evidence"
86
87	1. Navigate to the hypothesis in `.fpf/knowledge/L2/`
88	2. Re-run validation to create fresh evidence
89
90	#### Deprecate
91
92	User: "Deprecate the auth module decision"
93
94	1. Move hypothesis from L2 to L1 (or L1 to L0)
95	2. Create deprecation record:
96
97	```markdown
98	# In .fpf/evidence/deprecate-auth-module-2025-01-15.md
99	---
100	id: deprecate-auth-module-2025-01-15
101	hypothesis_id: auth-module
102	action: deprecate
103	from_layer: L2
104	to_layer: L1
105	created: 2025-01-15T10:00:00Z
106	---
107
108	# Deprecation: auth-module
109
110	Reason: Evidence expired, technology landscape changed
111
112	Next Steps: Run `/fpf:propose-hypotheses` to explore alternatives
113	```
114
115	3. Move the hypothesis file:
116	```bash
117	mv .fpf/knowledge/L2/auth-module.md .fpf/knowledge/L1/auth-module.md
118	```
119
120	#### Waive
121
122	User: "Waive the benchmark until February"
123
124	1. Create waiver record:
125
126	```markdown
127	# In .fpf/evidence/waiver-benchmark-2025-01-15.md
128	---
129	id: waiver-benchmark-2025-01-15
130	evidence_id: ev-benchmark-2024-06-15
131	waived_until: 2025-02-01
132	created: 2025-01-15T10:00:00Z
133	---
134
135	# Waiver: ev-benchmark-2024-06-15
136
137	Evidence: ev-benchmark-2024-06-15
138	Hypothesis: redis-caching
139	Waived Until: 2025-02-01
140	Rationale: Migration pending, will re-run after completion
141
142	Accepted By: User
143	Created: 2025-01-15
144
145	WARNING: This evidence returns to EXPIRED status after 2025-02-01.
146	```
147
148	---
149
150	## Natural Language Usage
151
152	You don't need to memorize evidence IDs. Just describe what you want.
153
154	### Example Workflow
155
156	```
157	User: /fpf:decay
158
159	Agent shows report with stale evidence
160
161	User: Waive the benchmark until February, we'll re-run it after the migration.
162
163	Agent: Creating waiver for ev-benchmark-2024-06-15 until 2025-02-01.
164	Rationale: "Re-run after migration"
165
166	[Creates .fpf/evidence/waiver-benchmark-2025-01-15.md]
167
168	User: The vendor API is being discontinued. Deprecate that decision.
169
170	Agent: Deprecating hypothesis-vendor-api from L2 to L1.
171	[Moves file, creates deprecation record]
172
173	Next step: Run /fpf:propose-hypotheses to explore alternatives.
174	```
175
176	---
177
178	## WLNK Principle
179
180	A hypothesis is STALE if any of its evidence is expired (and not waived).
181
182	This is the Weakest Link (WLNK) principle: reliability = min(all evidence). One stale

People who liked this also viewed

6 picks

Type