Bring security data into one structure
Internal product research scaffold for “Bring security data into one structure”. Questions and product/code evidence needed before public copy can be written.
Working research scaffold. This page lists questions for Product and Engineering; it does not confirm that the feature is available. The current foundation marks detailed first-party collection, proof-pack generation, buyer inspection, and AI-assisted response preparation as planned. Verify each answer against the released Mockup product and its code before turning it into a public capability claim.
Questions to answer
- What records does Aeptus treat as the same entity when sources use different names or identifiers?
- Which canonical objects and relationships connect systems, services, evidence, owners, and requests?
- How are duplicate, conflicting, or incomplete records represented and resolved?
- Which values are copied from a source and which are normalized or derived?
- Can a user trace a structured record back to the original source record?
Product and code information needed
- Current database schemas, migrations, domain models, and API contracts for the relevant records.
- Source-to-canonical mapping code, identifier rules, normalization logic, and duplicate/conflict handling.
- Tenant and entity relationship constraints plus tests using sanitized examples from more than one source.
- Fields that preserve original values, derived values, source IDs, and transformation history.