AGENT SKILL

basis-proof

Prove cost basis and realized gain from replayable acquisition lots instead of treating missing basis as zero. Use for sells, disposals, FIFO/LIFO/specific-lot analysis, tax-lot verification, oversold positions, or realized P&L where the system must show which lots support the result.

License 许可
Apache-2.0
所属仓库
SVRN-AGNT/Dale-OS
最近更新
2026-11-14
Stars
★ 1
Forks
0

01 前言 Front Matter

name
basis-proof
description
Prove cost basis and realized gain from replayable acquisition lots instead of treating missing basis as zero. Use for sells, disposals, FIFO/LIFO/specific-lot analysis, tax-lot verification, oversold positions, or realized P&L where the system must show which lots support the result.

02 资源文件 4

03 SKILL.md 正文

Basis Proof

Rule

No basis, no profit.

Workflow

  1. Order economic events by the canonical economic date, not arbitrary import time.
  2. Replay acquisitions and disposals under the lot method the account actually applied. If that method is unknown, do not assume one; stop when the choice would change the result, and pass method to the script explicitly rather than relying on its default.
  3. For each disposal, show shares requested, shares supported, source lots, proven basis, and any unsupported remainder.
  4. If shares sold exceed replayable shares, classify the disposal as unverified/oversold. Partial basis does not make the entire gain verified.
  5. Never coerce missing basis to zero in realized-gain arithmetic.
  6. Preserve holding-period provenance separately from basis if the dates needed for term are incomplete.

Deterministic companion

When structured JSON is available, prefer scripts/basis_proof.py for the mechanical check. Treat its output as a constraint on reasoning, not as permission to invent missing classifications. Run it from the skill directory with JSON on stdin. Read references/DETERMINISTIC_INPUT.md when you need the input contract.

Falsify it

Try to replay the disposal against real acquisition lots. If sold quantity exceeds provable lots or basis is missing, realized gain is not proven.

Stop conditions

  • The lot method is unknown and would materially change the result.
  • A disposal has unsupported quantity.
  • Required acquisition dates or basis values are unknown.

A stop is an output, not an excuse. State what evidence or authority would unblock the work.

Output

DISPOSAL · LOTS CONSUMED · SUPPORTED SHARES · PROVEN BASIS · REALIZED RESULT or WITHHELD · UNRESOLVED REMAINDER.

Keep the report short enough to act on. Preserve hard facts, unknowns, and blockers.

04 同仓库更多 Skills

SVRN-AGNT
SVRN-AGNT/Dale-OS

verify-before-cite

Live-verify work state before reporting or relying on it, and reconcile every place that state is recorded. Use before a status report, standup, handoff, or "what's open" answer; when a tracker, queue, memory note, or prior session says something is pending, merged, shipped, or blocked; after any merge, release, or promotion; or when records in two places disagree. Do not use to judge whether a claim about data or numbers is proven.

★ 1
SVRN-AGNT
SVRN-AGNT/Dale-OS

truth-boundary

Enforce provenance and uncertainty boundaries. Use when a system mixes observed, authoritative, user-attested, derived, estimated, inferred, reconstructed, or unknown values; when missing data could become zero; or when downstream output may overstate certainty. Also use when told to fill a missing, failed, or empty value with zero, a default, or a guess so the work can keep going.

★ 1
SVRN-AGNT
SVRN-AGNT/Dale-OS

systemic-bug-instinct

Use first, before reading, searching or editing code, whenever a defect, wrong value or balance, stale state, edge-case failure, broken workflow, or misleading UI is reported and a fix is requested, even when the request names the one file to patch. Diagnoses the bug as a possibly systemic failure to find the root mechanism, failure class, blast radius across sibling consumers, fix location, and regression guard. Do not use for a one-line typo or syntax fix, for two components that disagree about one concept (use seam-audit), for a dense screen whose value may be a presentation problem (use operator-ui-audit), or for financial records that contradict each other (use accounting-integrity).

★ 1
SVRN-AGNT
SVRN-AGNT/Dale-OS

swarm

Design and run the smallest effective multi-agent harness for complex work. Use when the user explicitly says SWARM or asks for a swarm, multi-agent workflow, adaptive orchestration, harness design, parallel investigation, independent falsification, architecture reconciliation, broad audit, competing root-cause hypotheses, or high-risk work that benefits from independent reasoning lanes. Do not use for trivial edits or linear tasks one agent can complete cheaply; the best swarm may use zero subagents. SWARM grants orchestration, not broader implementation, merge, deploy, credential, financial, or destructive authority.

★ 1
SVRN-AGNT
SVRN-AGNT/Dale-OS

shipping-lanes

Design, run, or adopt a pipeline in which agent-written changes are reviewed and merged without a person in the routine loop, with review and landing matched to each change's risk. Use when setting up or changing how PRs get reviewed and merged by agents; when every change waits on one person, or none gets reviewed; when a reviewer is only reached if the author asks for it; when docs and permission changes take the same path; or when bringing a new repository onto the shared shipping system. Do not use to decide whether one specific merge is authorised (use merge-authority), to judge a finished-looking result (use false-competence-check), or to prove a single guard is reached (use reachability-proof).

★ 1
SVRN-AGNT
SVRN-AGNT/Dale-OS

seam-audit

Audit the boundary where two components represent the same concept, because each side can pass its own tests while the combined system is wrong. Use when a value looks coherent but is wrong, when a projection or compatibility view stands in for a full record, when sync or merge involves deletes, when status codes or result shapes cross a boundary, or when "unknown" may become zero, false, or success as it crosses between two components. Do not use for a defect inside one component (use systemic-bug-instinct), for grading one claim's certainty (use truth-boundary), or for a financial repair's preview and commit (use ledger-repair).

★ 1