timothynn / timothynn/aviation-intelligence
P0: Build generic inspection case service
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 17m
- Merged PRs (30d)
- 4
Description
Implement the shared inspection service around the domain types in packages/inspection-domain.
Support planning, checklist items, evidence, findings, corrective actions, verification, closure and audit events.
Add scheme adapters without embedding SAFA/USOAP/IOSA-specific rules in core types.
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 the domain types in packages/inspection-domain and map how planning, checklist items, evidence, findings, corrective actions, verification, closure, and audit events should fit together. Define the service boundary before adding scheme adapters, keeping SAFA, USOAP, and IOSA-specific rules outside the core types. Done means the shared inspection lifecycle and adapter structure support all listed capabilities without scheme-specific logic in core.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100