metadata-lineage-design
Define business, technical, and operational metadata, ownership, source-to-target and transformation lineage, catalog publication, impact analysis, and auditability. Use for catalogs, lineage, dataset handoffs, change analysis, or discoverability requirements.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- metadata-lineage-design
- description
- Define business, technical, and operational metadata, ownership, source-to-target and transformation lineage, catalog publication, impact analysis, and auditability. Use for catalogs, lineage, dataset handoffs, change analysis, or discoverability requirements.
03 SKILL.md 正文
Metadata and Lineage Design
Outcome
Create a minimum metadata and lineage contract that supports discovery, operation, impact analysis, quality, security, and audit.
Method
- Identify the dataset, event, field, pipeline, report, model, or control whose metadata is governed.
- Define business metadata such as meaning, owner, steward, domain, grain, terms, classification, and intended use.
- Define technical metadata such as schema, types, keys, locations, formats, versions, partitions, and interfaces.
- Define operational metadata such as runs, freshness, volume, quality status, incidents, SLOs, retention, and support route.
- Capture source-to-target and transformation lineage at the lowest level needed for impact analysis. Mark observed, declared, and inferred lineage distinctly.
- Define capture points, automation, update timing, validation, versioning, and responsible owner.
- Define catalog publication, search terms, access request route, and the consumer-visible indicators for quality and freshness.
- Test impact analysis in both directions for one representative field and one dataset-level change.
Shared resources
Load only the resources needed for the current task. The links resolve inside the current agent package.
../../templates/lineage-record.yaml../../templates/source-to-target-mapping.md../../references/metadata-minimum-standard.md../../references/terminology-glossary.md../../references/evidence-citation-guide.md
Completion check
Metadata is incomplete when ownership is a team name with no response route, lineage omits transformations, or impact analysis cannot identify affected consumers.
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.