Issue and repo context
The agent reads manifests, nearby code, tests, dirty state, and local conventions.
Wish
A serious coding agent is not just a code generator. It reads the repository, respects user work, proposes a scoped patch, names tests, repairs CI, explains rollback, and never uses unsafe shortcuts unless explicitly authorized.
Software engineers, platform teams, AI coding-agent builders, CI maintainers, and technical leaders.
Thesis
This domain hub is designed for two jobs at once: educate serious users and create better training direction for Hermon adapters. The same vocabulary appears in tutorials, demos, eval rubrics, and model output contracts.
Architecture Map
Hermon Code proposes engineering work; Wish and MapleAI decide read/write permissions, command execution, tests, deployment, and rollback.
The agent reads manifests, nearby code, tests, dirty state, and local conventions.
The model returns files_to_inspect, proposed_changes, tests, rollback, and denied actions.
The runtime authorizes reads, writes, commands, service restarts, and deployment separately.
Tests, smoke checks, review notes, and rollback proof become durable engineering evidence.
Research Questions
What should a coding model output before it edits any file?
How can repository context, tests, and rollback be made mandatory rather than optional?
How should coding agents handle user changes, secrets, destructive commands, and deployment authority?
Which evals prove that an adapter is useful for real engineering work rather than toy code generation?
Core Concepts
The model should inspect package files, local conventions, tests, service boundaries, and existing changes before proposing edits.
A useful response names files_to_inspect, proposed_changes, tests, rollback, actions, review boundaries, and residual risk.
Secret exposure, destructive git commands, unrelated cleanup, and unauthorized deployment are safety failures, not productivity features.
The current Code lane improves by failing public contract probes, generating targeted data, training a new adapter, and promoting only when probes pass.
Tutorial Series
Each lesson includes foundations, applied architecture, a lab prompt, evaluation checks, and an output contract that can become training data or demo validation.
The mandatory fields Hermon Code should return before work becomes executable.
Open lessonHow a coding agent learns the shape of a codebase before changing it.
Open lessonHow Hermon Code should move from a failing symptom to a verified fix.
Open lessonHow coding agents should prepare production changes without owning production authority.
Open lessonHow Hermon Code should refuse unsafe engineering shortcuts while staying helpful.
Open lessonHow Hermon Code becomes a product surface for AI software work under Maple authority.
Open lessonIndustrial Map
Diagnose routes, clients, services, state, and tests; patch only the narrow surface; verify the fix.
WishRead failing logs, reproduce locally, patch the cause, rerun targeted checks, and report residual risk.
WishPrepare build checks, health checks, smoke tests, restart steps, and rollback plans.
WishPreserve user changes, ignore unrelated dirty files, avoid metadata churn, and keep commits reviewable.
WishReading Map
Use the tutorials as user education, data-generation prompts, eval design, and demo scenarios for the next Hermon adapter cycle.