Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
- Created project for StellaOps.Scanner.Analyzers.Native.Tests with necessary dependencies. - Documented roles and guidelines in AGENTS.md for Scheduler module. - Implemented IResolverJobService interface and InMemoryResolverJobService for handling resolver jobs. - Added ResolverBacklogNotifier and ResolverBacklogService for monitoring job metrics. - Developed API endpoints for managing resolver jobs and retrieving metrics. - Defined models for resolver job requests and responses. - Integrated dependency injection for resolver job services. - Implemented ImpactIndexSnapshot for persisting impact index data. - Introduced SignalsScoringOptions for configurable scoring weights in reachability scoring. - Added unit tests for ReachabilityScoringService and RuntimeFactsIngestionService. - Created dotnet-filter.sh script to handle command-line arguments for dotnet. - Established nuget-prime project for managing package downloads.
1.8 KiB
1.8 KiB
Excititor Worker Charter
Mission
Run Excititor background jobs (ingestion, linkset extraction, dedup/idempotency enforcement) under the Aggregation-Only Contract; orchestrate Core + Storage without applying consensus or severity.
Scope
- Working directory:
src/Excititor/StellaOps.Excititor.Worker - Job runners, pipelines, scheduling, DI wiring, health checks, telemetry for background tasks.
Required Reading
docs/modules/excititor/architecture.mddocs/modules/excititor/vex_observations.mddocs/ingestion/aggregation-only-contract.mddocs/modules/excititor/implementation_plan.md
Roles
- Backend/worker engineer (.NET 10).
- QA automation (background job + integration tests).
Working Agreements
- Track task status in sprint files; log notable operational decisions in Execution Log.
- Respect tenant isolation on all job inputs/outputs; never process cross-tenant data.
- Idempotent processing only: guard against duplicate bundles and repeated messages.
- Offline-first; no external fetches during jobs.
- Observability: structured logs, counters, and optional OTEL traces behind config flags.
Testing & Determinism
- Provide deterministic job fixtures with seeded clocks/IDs; assert stable ordering of outputs and retries.
- Simulate failure/retry paths; ensure idempotent writes in Storage.
- Keep timestamps UTC ISO-8601; inject clock/GUID providers for tests.
Boundaries
- Delegate domain logic to Core and persistence to Storage.Mongo; avoid embedding policy or UI concerns.
- Configuration via appsettings/environment; no hard-coded secrets.
Ready-to-Start Checklist
- Required docs reviewed.
- Test harness prepared for background jobs (including retry/backoff settings).
- Feature flags defined for new pipelines before enabling in production runs.