ELYRAON Repo Maintainer

ELYRAON Repo Maintainer is a hosted autonomous repository-maintenance service powered by ELYRAON's private NOVA/FETT infrastructure.

It analyzes an authorized repository, identifies actionable engineering work, implements qualified fixes, runs verification, and returns a verified patch together with a maintenance and verification report.

The customer receives the maintenance results, not the private NOVA/FETT backend.

What it does

• Analyzes an authorized code repository
• Identifies actionable maintenance work
• Plans implementation work
• Produces code changes
• Runs verification against the repository's test suite
• Returns a qualified patch/diff
• Returns findings and a verification report
• Preserves prior results for later review
• Supports recurring maintenance runs within the customer's subscription limits

Current verified scope

The current 0.1.0 service has been verified end to end on Python repositories using pytest.

The production flow has been proven through:

repository authorization → ingestion → planning → dispatch → implementation → verification → patch generation → customer-facing result retrieval

A full public production canary completed successfully through https://api.elyraon.com.co.

How it works

The Agensi skill communicates with the hosted ELYRAON Repo Maintainer API.

The private NOVA/FETT implementation remains on ELYRAON infrastructure and is not distributed to customers.

Customers authenticate using an ELYRAON-issued service key.

Repositories are registered as pinned snapshots. Public repositories can be explicitly refreshed. Private repositories require authorized repository credentials for refresh/access.

What the customer receives

• Findings
• Maintenance-run status
• Verified code changes
• Patch/diff output
• Verification results
• Maintenance report

The customer reviews and applies the patch and opens any pull request themselves.

Current subscription model

The initial service is intentionally bounded. The backend currently supports:

• One active customer worker globally at a time
• Per-tenant usage and repository limits
• Queued work when capacity is occupied
• Fail-closed handling when multi-task patches cannot be combined safely

Capacity limits affect when accepted customer work runs, not whether the internal FETT system changes its eligibility policy.

Security and isolation

• Customer API access is tenant-scoped.
• Service keys are stored only as hashes.
• Repository credentials are not persisted unnecessarily and are not logged.
• Cross-tenant repository, run, patch, and verification access has been regression-tested and returns not-found behavior.

The service does not claim hardened OS-level isolation for arbitrary untrusted repository execution. Customer jobs currently run on ELYRAON's controlled backend infrastructure with the documented service boundary.

Requirements

• Active ELYRAON Repo Maintainer subscription
• ELYRAON-issued service key
• Repository the customer is authorized to access
• For private repositories, authorized repository credentials
• Production API access to https://api.elyraon.com.co

Verified production checks

Public TLS, public end-to-end canary, authorization, repository registration, planning, dispatch, implementation, verification, patch retrieval, verification report retrieval, tenant isolation, key rotation/revocation, inactive subscription handling, explicit repository refresh, and queueing under one-worker capacity: all PASS. Two simultaneous public requests were tested; one ran and one queued, then both completed. Current package client tests: 7 passed. Current commercial backend tests: 30 passed.

Authentication & subscription

Requires an ELYRAON-issued service key tied to an active Repo Maintainer subscription. In v0.1.0, service keys are provisioned and subscriptions are activated manually by ELYRAON; ELYRAON supplies the service credential after subscription activation. The skill package itself contains no backend access.