govfolio-saf-authoring

Author append-only source-authority memory separating trusted and untrusted evidence.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/ssmleo/govfolio --skill govfolio-saf-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: govfolio-saf-authoring
Source: https://github.com/ssmleo/govfolio/tree/main/.agents/skills/govfolio-saf-authoring
Command: npx skills add https://github.com/ssmleo/govfolio --skill govfolio-saf-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps in authoring append-only source-authority memory, separating trusted and untrusted evidence.

Core Features & Use Cases

  • Append-Only Memory: Allows for the creation of a secure, append-only memory store.
  • Evidence Separation: Provides the capability to distinguish between trusted and untrusted evidence.
  • Use Case: For applications that require maintaining a tamper-evident record of transactions or data modifications.

Quick Start

Author new source-authority memory entries with the govfolio-saf-authoring skill.

Frequently Asked Questions about govfolio-saf-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is append-only source-authority memory for secure logging?

Append-only source-authority memory is a tamper-evident data store that maintains verifiable data integrity by preventing modifications to existing records. It separates trusted and untrusted evidence to ensure reliable audit trails for transaction history.

How do I separate trusted and untrusted evidence in an audit trail?

You can separate trusted and untrusted evidence by authoring memory entries with a source-authority mechanism. This capability distinguishes between verified and unverified data, ensuring secure logging records maintain clear evidence separation for auditability.

When do I need source-authority memory for data integrity?

You need source-authority memory when your application requires a tamper-evident record of transactions or data modifications. It is designed for systems requiring verifiable data integrity and secure logging, ensuring historical records cannot be altered.

Does append-only memory work for building verifiable audit trails?

Yes, append-only memory is designed specifically for creating secure audit trails. It allows you to append new entries while preventing modifications to existing data, providing a tamper-evident record that ensures verifiable data integrity.

What is the best way to create a tamper-evident record of data modifications?

The best way to create a tamper-evident record is by using an append-only memory store with evidence separation. This approach differentiates between trusted and untrusted evidence, providing verifiable data integrity for secure logging and audit trails.

Are there limitations to using append-only memory for secure logging?

A limitation of append-only memory is that existing records cannot be modified or deleted, meaning corrections require new appended entries. This design ensures data integrity but may require adjusting workflows accustomed to in-place data updates.