-
Notifications
You must be signed in to change notification settings - Fork 23
Add explicit metadata for synthetic-only fixture assumptions #64
Copy link
Copy link
Closed
Labels
GrantFox OSSIssue tracked in GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardIssue may be eligible for a GrantFox rewardThird CampaignCampaign: Third CampaignCampaign: Third Campaignarea: fixturesDestination and transaction fixture coverageDestination and transaction fixture coveragearea: validationFixture schema and integrity checksFixture schema and integrity checksenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomers
Description
Activity
Metadata
Metadata
Assignees
Labels
GrantFox OSSIssue tracked in GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardIssue may be eligible for a GrantFox rewardThird CampaignCampaign: Third CampaignCampaign: Third Campaignarea: fixturesDestination and transaction fixture coverageDestination and transaction fixture coveragearea: validationFixture schema and integrity checksFixture schema and integrity checksenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomers
Category
Good First
Summary
Add and validate a per-destination field distinguishing synthetic-only fixtures from any future network-visible fixture.
Current Behavior
Synthetic and unfunded status is documented globally, not recorded per entry.
Problem
Future contributors can add entries with different lifecycle assumptions without recording them explicitly.
Why This Matters
Per-fixture status prevents consumers from treating synthetic labels as live Horizon truth.
Proposed Scope
Add a constrained field such as
fixture_status: "synthetic-only", populate current entries, and validate allowed values.Acceptance Criteria
Technical Considerations
The field is additive; coordinate with the vendored adapter schema before release.
Testing Requirements
Cover missing, invalid, and valid status values.
Cross-Repository Impact
Adapter fixture schema compatibility must be checked.
Out of Scope
Do not perform Horizon lookups; see issue #44.
Complexity
Localized schema and documentation change.
Impact
Medium — improves data safety.
Suggested Labels
good first issue,area: fixtures,area: validation