Skip to content

Latest commit

 

History

History
30 lines (21 loc) · 4.18 KB

File metadata and controls

30 lines (21 loc) · 4.18 KB

Agentique Companion Docs Overview

Agentique.io is a platform for preparing, reviewing, publishing, and displaying public AI resource listings. Agentique companion docs describe the public developer kit and creator kit for that platform.

These docs help external creators prepare public resources before entering the agentique.io upload flow, validate package structure with public tooling, inspect non-static lane descriptors, review parser/variant metadata, review agent-native preparation metadata, review portable profile metadata, review graph/block metadata, review skill-source or role/plugin candidates with local readiness reports, review uploader behavior, prepare local draft or patch output, and display resource status through public readback after platform publication.

The docs explain resource manifests, registry trust metadata, parser/variant metadata, agent-native preparation metadata, portable profile metadata, graph/block review metadata, skill-source and role/plugin candidate checks, skill packages, workflow templates, non-static lane examples, distribution mode choices, uploader boundaries, trust, parser/variant and agent-native readback, generated draft and patch/delta preparation, and support routing.

agentique.io owns upload, scan, review, consent, moderation, distribution state, and readback. Companion docs and local tools only help prepare content for that platform-owned flow.

Local validation is not platform approval. Local validation is not safety certification. Public readback reflects the platform state that agentique.io exposes, and stale or unavailable readback must be shown as stale or unavailable.

Preparation Flow

  1. Draft a resource manifest.
  2. Add package metadata and inventory.
  3. Choose a distribution mode that matches the content.
  4. Run local static checks when available.
  5. Add parser/variant metadata only when it is static, source-only, and backed by no-execution evidence.
  6. Add agent-native metadata only for public namespace, non-certifying provenance labels, source-only or guidance-only install guidance, public boundary labels, and resolver intent.
  7. Add portable profile metadata only when it is descriptor-only, no-execution, and backed by explicit generated-output provenance.
  8. Add graph/block metadata only when it is descriptor-only, no-execution, and limited to static topology, block, ledger, artifact, fixture, or drift metadata.
  9. Run upload-candidate, package-dry-run, or source-no-go checks for skill-source or role/plugin candidates when provenance, license, runtime-risk, or readiness needs a local report.
  10. Use uploader plan, import-plan, variant-plan, agent-native-plan, draft, or patch commands for local review-only preparation when useful.
  11. Enter the platform-owned upload flow on agentique.io, or review an uploader session when explicitly configured with platform API access and checkpoint-ready package metadata.
  12. Wait for platform scan, review, consent, moderation, publication, and readback.

Public Boundaries

Companion docs and tools do not publish, edit, delete, moderate, approve, certify, host, resolve, or execute resources. Parser/variant metadata, agent-native metadata, portable profile metadata, graph/block metadata, skill-source and role/plugin readiness reports, descriptor dry-runs, No-Go reports, and uploader dry-runs are local preparation evidence only. Parser/variant package changes are included in the coordinated package releases after hosted CI, package publication, registry readback, and install-smoke. Canonical catalog envelope fixes, ticket-backed byte-transfer fixes, agent-native schema/validator/readback/uploader dry-run surfaces, portable profile surfaces, and graph/block surfaces are published in the owner-approved coordinated 0.2.2 package set. Runtime claims and direct-install claims remain disabled. Owner-approved disposable byte-transfer evidence is recorded for a public catalog resource. The uploader package is review-only; authenticated review-session access and final resource publication remain platform-owned and account/token gated. Public issue threads are for docs and tooling questions, not unsafe reports, raw imported content, credentials, private source archives, or private account matters.