docs(darwin): agent-developer guide for the hardening policy#209
Open
ciphr wants to merge 1 commit into
Open
Conversation
Persona: Agent Developer. Type: Guide. Path: developer-guide/adapt/hardening-policy.mdx Documents the HardeningPolicy feature (DAR-14/15/16/17) for developers who run Darwin as a module in a Kubernetes cluster: attaching a policy to an evolution job over REST and via the SDK, the policy schema (attribution / mutation / tradeoff sub-policies), None = default behavior, and the extra="forbid" validation. Every code example and claim was verified against shipped source: vijil-darwin origin/main (dc595d1, includes DAR-16's extra="forbid") and vijil-sdk main — schema fields/defaults/validators, the POST /v1/evolutions request and 202 response, the SDK call path, and the service-darwin in-cluster URL. Steelman docs-rubric review: PASS. Vale style applied by hand (Title Case headings, no contractions, component naming) — Vale is not installed locally, so CI / the tech-write review should run it. The page is intentionally NOT registered in docs.json navigation and the placement under developer-guide/adapt/ is a proposal: IA, nav, and release gating (the feature is pre-release) are left for the tech-writer review. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A new Agent Developer Guide: Steer how Darwin hardens your agent — at
developer-guide/adapt/hardening-policy.mdx.It documents the HardeningPolicy feature (shipped across DAR-14/15/16/17) for developers who run Darwin as a module in their own Kubernetes cluster: how to attach a policy to an evolution job over REST and via the SDK, the full policy schema, the
None= default-behavior contract, and theextra="forbid"validation.For the tech-write review
This is not ready to publish as-is — it needs your review on three things I deliberately left for you:
developer-guide/onmainyet (it hasevaluateandprotect, but nothing for the adapt/improve stage). I placed this under a newdeveloper-guide/adapt/directory as a proposal. Move/rename as the IA dictates.docs.json, so it will not appear in the sidebar. Decide its nav group when you settle placement..draft.mdx(excluded from the build per the repo's draft convention) until the feature ships.Vale was not run — it is not installed in my environment. I applied the documented
VijilStylerules by hand (Title Case headings, no contractions, H2/H3 only, component naming), but please runvale developer-guide/adapt/hardening-policy.mdxas the authoritative check.Substance verification (done)
Every code example and factual claim was traced to shipped source before writing — no fabrication:
vijil-darwinorigin/maindc595d1— which includes DAR-16, so theextra="forbid"/ "typos fail loud" claim is true.POST /v1/evolutionsrequest body +202CreateJobResponse+ the genome prerequisite, againstapi/routes/jobs.py.EvolutionsGeneratedResource+VijilHTTPcall path, and the caveat thatclient.jobsroutes through the Console (not Darwin-direct), againstvijil-sdk.service-darwinagainst the Helm chart.postgres_job_repository._to_row.A two-reviewer steelman pass against the docs rubric returned PASS after this verification. (An earlier pass false-flagged the schema because it read a stale local checkout; syncing to
origin/mainresolved it — the doc matches shipped code.)Do not merge
Hold for tech-writer review + a release-timing decision.
🤖 Generated with Claude Code