data-engineering/AGENTS.md

Agent Guide

This repository is a data-engineering knowledge base, not an application runtime repo.

Mission

Help organize and verify business-domain analysis, technical implementation analysis, data lineage, evidence, and visualization-ready artifacts for AIGC-related modules.

Default Workflow

1. Read this file, README.md, and the relevant domains/<domain>/README.md.
2. If starting a new domain, create or update 01-recon-notes.md before detailed analysis.
3. Separate business logic, technical implementation, data lineage, and verification notes.
4. Prefer code and DB verification over assumptions.
5. Record stale, partial, blocked, or unverified claims explicitly.
6. Keep domain-local facts under domains/<domain>/.
7. Keep cross-domain joins and total graphs under integrated/.

Safety Rules

• Do not print or copy raw passwords, tokens, AK/SK, API keys, or cookie values into reports.
• DB verification should use read-only queries when possible.
• If a table/file contains sensitive fields, describe the field existence and role without exposing secret values.
• Do not silently overwrite manually curated Excel or Markdown files.
• Do not move existing analysis files unless the user explicitly asks for that move.

Repository Roles

• skills/ defines reusable methods.
• templates/ defines fill-in artifacts for new business domains.
• schemas/ defines the target machine-readable lineage format.
• domains/ stores per-domain analysis and data files.
• integrated/ stores the cross-domain graph and aggregate artifacts.
• archive/ stores old or superseded material.

Expected Domain Files

Each business domain should eventually contain:

• README.md
• 01-recon-notes.md
• 02-business-logic.md
• 03-technical-implementation.md
• 04-data-lineage.md
• 05-verification.md
• domain-specific .xlsx files
• optional lineage.snapshot.json

Current Domain Names

• clustering
• pattern-v2
• demand-agent
• external-sources
• building-system-agent
• search-agent