Praxis Java HTTP Corpus Publication
Publish a corpus entry only after the Java resource contract is proven. The corpus
indexes reproducible HTTP evidence for humans and AI; it does not become a second
source of schemas, metadata, authorization, or business behavior.
Start From Canonical Evidence
Inspect the owning starter/Quickstart resource, controller, schemas, HTTP proof,
security/header requirements, and existing corpus entries. Classify the gap as
already supported, poorly materialized, partial, or a real corpus gap. Fix a
backend contract defect in its canonical owner before changing the example.
Choose one evidence slice: schema/discovery, read/filter, option reload,
action/surface/capability, stats/export, or a protected write. Preserve only
sanitized fixtures and deterministic non-secret headers/payloads.
Publish The Example
- Add the request and payload under the corpus conventions and record the
canonical
sourceOfTruth. Do not hard-code a workaround URL or invent headers.
- Register every artifact in
examples.manifest.json with method, endpoint,
payload references, responseShapeHint, safety state, auth/header needs, and
evidence flags. Keep llmOperational, protectedContract, and referenceOnly
mutually exclusive.
- Put safe, read-oriented, confirmed examples in the LLM lane only after the
published backend proof succeeds. Keep destructive writes and protected flows
out of the default lane; they may document contracts without becoming default
operational prompts.
- Regenerate derived LLM material from the manifest. Never hand-edit generated
LLM surface files.
- When smoke evidence disagrees with Java proof, classify runtime/corpus/canonical
drift and repair the owner. Do not weaken flags to make a failing endpoint look
operational.
Read corpus-publication-matrix.md
when choosing example layer, required manifest evidence, or smoke gate.
Boundaries And Validation
praxis-metadata-starter owns schema/discovery/metadata semantics.
praxis-api-quickstart owns reference-host HTTP behavior and proof.
praxisui-http-examples owns derived request files, manifest claims, generated
LLM surface, and corpus validation.
Run npm run verify:manifest; regenerate LLM surface when affected; run the
narrowest relevant public/auth/LLM smoke. State whether validation reached a
published backend or only checked structure. Use praxis-java-contract-conformance
when the Java resource itself still lacks evidence.
Companion Skills
praxis-java-quickstart-proof: obtain the operational Java proof first.
praxis-http-examples-corpus-manifest: manifest and evidence flags.
praxis-http-examples-contract-surfaces: request/header/payload semantics.
praxis-http-examples-llm-smoke: safe LLM lane and smoke selection.
Close with canonical owner, example layer, manifest evidence, generated artifacts,
smoke result, and any unresolved backend gap. A corpus entry is ready when it
helps reproduce a real contract without making an unsafe flow look routine.
1---2name: praxis-java-http-corpus-publication3description: "Use when publishing or auditing a Java/Praxis resource proof in praxisui-http-examples: canonical Quickstart/starter HTTP evidence, request and payload files, examples.manifest.json, sourceOfTruth, safety classification, responseShapeHint, LLM operational lanes, protected contracts, manifest generation, and focused corpus smokes."4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-java-http-corpus-publication6---78# Praxis Java HTTP Corpus Publication910Publish a corpus entry only after the Java resource contract is proven. The corpus11indexes reproducible HTTP evidence for humans and AI; it does not become a second12source of schemas, metadata, authorization, or business behavior.1314## Start From Canonical Evidence1516Inspect the owning starter/Quickstart resource, controller, schemas, HTTP proof,17security/header requirements, and existing corpus entries. Classify the gap as18already supported, poorly materialized, partial, or a real corpus gap. Fix a19backend contract defect in its canonical owner before changing the example.2021Choose one evidence slice: schema/discovery, read/filter, option reload,22action/surface/capability, stats/export, or a protected write. Preserve only23sanitized fixtures and deterministic non-secret headers/payloads.2425## Publish The Example26271. Add the request and payload under the corpus conventions and record the28 canonical `sourceOfTruth`. Do not hard-code a workaround URL or invent headers.292. Register every artifact in `examples.manifest.json` with method, endpoint,30 payload references, `responseShapeHint`, safety state, auth/header needs, and31 evidence flags. Keep `llmOperational`, `protectedContract`, and `referenceOnly`32 mutually exclusive.333. Put safe, read-oriented, confirmed examples in the LLM lane only after the34 published backend proof succeeds. Keep destructive writes and protected flows35 out of the default lane; they may document contracts without becoming default36 operational prompts.374. Regenerate derived LLM material from the manifest. Never hand-edit generated38 LLM surface files.395. When smoke evidence disagrees with Java proof, classify runtime/corpus/canonical40 drift and repair the owner. Do not weaken flags to make a failing endpoint look41 operational.4243Read [corpus-publication-matrix.md](references/corpus-publication-matrix.md)44when choosing example layer, required manifest evidence, or smoke gate.4546## Boundaries And Validation4748- `praxis-metadata-starter` owns schema/discovery/metadata semantics.49- `praxis-api-quickstart` owns reference-host HTTP behavior and proof.50- `praxisui-http-examples` owns derived request files, manifest claims, generated51 LLM surface, and corpus validation.5253Run `npm run verify:manifest`; regenerate LLM surface when affected; run the54narrowest relevant public/auth/LLM smoke. State whether validation reached a55published backend or only checked structure. Use `praxis-java-contract-conformance`56when the Java resource itself still lacks evidence.5758## Companion Skills5960- `praxis-java-quickstart-proof`: obtain the operational Java proof first.61- `praxis-http-examples-corpus-manifest`: manifest and evidence flags.62- `praxis-http-examples-contract-surfaces`: request/header/payload semantics.63- `praxis-http-examples-llm-smoke`: safe LLM lane and smoke selection.6465Close with canonical owner, example layer, manifest evidence, generated artifacts,66smoke result, and any unresolved backend gap. A corpus entry is ready when it67helps reproduce a real contract without making an unsafe flow look routine.