data-integration-contracts
Define producer and consumer responsibilities, schema and semantic compatibility, delivery, freshness, versioning, deprecation, ownership, and escalation. Use whenever data crosses a system, domain, team, vendor, or organizational boundary.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- data-integration-contracts
- description
- Define producer and consumer responsibilities, schema and semantic compatibility, delivery, freshness, versioning, deprecation, ownership, and escalation. Use whenever data crosses a system, domain, team, vendor, or organizational boundary.
03 SKILL.md 正文
Data Integration Contracts
Outcome
Create a versioned contract that makes ownership and compatibility enforceable at the boundary rather than assumed inside downstream logic.
Method
- Name the dataset or event, producer, consumers, business purpose, authority, and grain.
- Define fields, types, meanings, units, nullability, identities, temporal semantics, classification, and valid ranges.
- Define transport, cadence, delivery guarantees, ordering, duplicate behavior, freshness, availability, and retention.
- Classify compatible and breaking changes. Define versioning, notification, test evidence, parallel-run, migration, and deprecation windows.
- Define producer obligations, consumer obligations, validation location, quarantine, replay, and reconciliation.
- Assign owners, support channel, severity rules, escalation path, and decision rights.
- Link the contract to source-to-target mapping, quality rules, metadata, lineage, SLOs, and security controls.
Review rules
- Do not use a schema as a substitute for semantics.
- Do not promise exactly-once delivery without defining the bounded system in which it holds.
- Do not make a consumer infer whether missing means unknown, not applicable, redacted, or delayed.
- Do not permit silent breaking changes.
Shared resources
Load only the resources needed for the current task. The links resolve inside the current agent package.
../../templates/data-contract.yaml../../templates/source-to-target-mapping.md../../references/metadata-minimum-standard.md../../references/naming-conventions.md
Output
Return the completed contract plus unresolved semantic, compatibility, ownership, and enforcement questions.
04 同仓库更多 Skills
twenty-year-land-plan
Apply the Bren discipline of evaluating every land and development decision on a twenty-year horizon, with a comprehensive plan for how the land, the community, and the surrounding public infrastructure evolve together. Deals optimized for a five-year exit are structurally different from deals that compound across generations; insist on knowing which kind you are making. Use when evaluating land, entitlements, master-planned development, or phasing decisions, and when separating five-year exit deals from generational holds.
thematic-gut-check
Apply the Gray discipline of identifying the structural theme behind every real estate deal, testing where that theme sits in its capital-flow lifecycle, and insisting that deals without a named theme — or deals late in a crowded theme — clear a higher bar. A mediocre deal in a strong theme usually beats a clever deal in a weak one. Use when naming the structural thesis behind a deal, judging whether that theme is early or crowded, and setting the bar the deal must clear.
supply-pipeline-gut-check
Apply the Zell discipline of grounding every real estate thesis in the local supply pipeline. Demand counts over adjectives — units under construction, units permitted, units proposed — and convert them into a forward absorption schedule. A deal that ignores the pipeline is a bet on a market you have not actually studied. Use when validating a market thesis, forecasting absorption and rent growth, or counting units under construction, permitted, and proposed.
ruin-scenario-mapping
Apply the Taleb discipline of identifying, for every real estate deal, the specific chain of events that produces ruin — permanent, unrecoverable capital loss — and verifying that no single such chain has non-trivial probability. Deals with any plausible ruin path must be restructured or abandoned. Use when sizing leverage, testing refinancing, covenant, and liquidity risk, or checking whether any single failure chain can permanently wipe out the position.
revenue-cost-architecture
Design a venture's revenue streams, pricing logic, cost structure, and unit economics so the business model has a coherent theory of value capture, not just value creation. Use after the value proposition and customer segment are set and before financial projections, when choosing a pricing model, calculating contribution margin or CAC payback, or checking whether the unit economics hold at scale.
replacement-cost-stress-test
Apply the Buffett discipline of pricing every real estate asset against the cost to rebuild it from scratch. The ratio of purchase price to replacement cost sets a ceiling on long-run downside: below replacement cost, new supply cannot profitably undercut you; at or above it, you are buying a liability disguised as an asset. Use when setting a purchase price, judging downside protection, or testing how exposed an asset is to newly built competing supply.