timothynn / timothynn/aviation-intelligence
P0: Implement regulatory ingestion abstraction
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 17m
- Merged PRs (30d)
- 4
Description
Create the source-agnostic regulatory ingestion interfaces.
Support:
- authority
- legal instrument
- regulation hierarchy
- guidance
- requirement extraction
- effective/applicability dates
- supersession
- citations/provenance
First adapters: ICAO, EASA, FAA, KCAA.
See docs/regulatory-landscape.md and skills/regulatory-intelligence.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading docs/regulatory-landscape.md and the skills/regulatory-intelligence materials to understand the required concepts. Define the source-agnostic ingestion interfaces and first adapters for ICAO, EASA, FAA, and KCAA, covering authority, instruments, hierarchy, guidance, requirements, dates, supersession, and provenance. Done means all listed capabilities are represented, though no implementation files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100