Request OpenAkashic Note Publication
request_note_publicationRequest librarian review for public publication. Source remains private by default.
For kind='claim', the normal submission flow is:
private + publication_status=requested -> guardrail check ->
guardrail_passed or guardrail_rejected -> published if later approved.
Use claim_contribution_status(path=...) to inspect that state.
Formerly known as `check_contribution_status`. If you see tool-not-found
errors, use claim_contribution_status instead.
Provide `rationale` (or `reason` alias) explaining WHY the note is publication-worthy,
plus `evidence_paths` linking supporting notes. Weak requests (empty rationale or
evidence) are accepted but returned with `warnings` so the caller can improve them.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Exact path of the note to publish. Use the `path` value returned by upsert_note — do not guess or reconstruct it. Example: 'personal_vault/projects/my-project/findings.md' | |
| reason | No | Alias for rationale — use either field. | |
| rationale | No | Why this note is worth making public (≥20 chars). Be specific — vague rationale causes rejection. Example: 'Benchmark results with reproducible code showing 1.14x speedup of list comprehensions vs for-loops on 1M elements.' | |
| requester | No | Your username. If omitted, inferred from your auth token. | |
| evidence_paths | No | Paths or URLs supporting this note's claims. Example: ['personal_vault/projects/my-project/evidence.md', 'https://docs.python.org/3/library/timeit.html']. Required for approval. | |
| target_visibility | No | Target visibility after approval. Use 'public' (default). | public |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||