Build the capability once.
Make it fit the next job.

01 · First reference block

{
  "design": {
    "accent": "#a84416",
    "placement": "inline"
  },
  "content": {
    "title": "Tell us what could work better."
  },
  "features": {
    "enabled": true,
    "audio": false,
    "photo": false,
    "screenshot": false,
    "video": false,
    "triage": true
  },
  "config": {
    "categories": [
      "general",
      "bug",
      "idea"
    ],
    "max_audio_bytes": 262144,
    "max_attachments": 4,
    "max_attachment_bytes": 5242880,
    "max_total_attachment_bytes": 10485760
  }
}

{
  "coverage": "No preview actions yet",
  "cost": {
    "status": "unknown"
  }
}

02 · Understand the connections

See the block.
Then see the workflow.

Real Archify diagrams describe the reference block and a proposed composition. Follow inputs, authorization, persistence, events and recovery. Planned workflow extensions are labeled inside the diagram.

03 · Capability map

Start with the job.
Find the reusable boundary.

A growing map of capabilities for portals, CRM, operations, enterprise connections and creative applications. A listing is a research or build decision, not a promise of available software.

04 · Telemetry is a capability

Every block should explain its work.

The common contract connects operating evidence across tools and workflows. Customers control collection, redaction, retention and destinations. Local diagnostics, managed evidence and advanced Intelligence can be packaged separately.

• block edition
• configuration identity
• tenant scope
• operation and result
• correlation and causation
• state transition
• latency
• retry and failure
• human intervention
• outcome evidence
• known or missing cost
• coverage and redaction

A captured event is not business acceptance or proof of causality. The first reference publishes its exact coverage; cross-tool Intelligence, richer tracing and enterprise retention remain development work.

05 · Skills on demand

Fetch the instructions
for the job in front of you.

Discover a compact summary, retrieve one version and pin its content hash. Gradia and selected open-source reference skills can be read over HTTP without installing a skill folder. Pinned source, license and static-screen status travel with each reference. Fetched instructions never grant tool permissions.

Private enterprise registries, organization policies, approval flows, revocation and metered distribution are planned. The service still stores versioned content; retrieval removes the local-install requirement. Commercial packaging is undecided. Composition planning deduplicates identical instruction hashes, pins selected versions and flags possible overlap; compatibility still requires evaluation.

Connected reference · Work Items 0.2

Turn feedback into a proposal.
Keep the human decision explicit.

An authenticated Feedback block can hand a selected revision to a configurable work-item API. Tenant, principal, edition and configuration checks guard the connection. An operator chooses when to accept the proposal and move it through the workflow.

1. 01 · Capture

   Read the authorized Feedback revision. Media stays in Feedback; this profile transfers text and source metadata.

2. 02 · Propose

   Create one source-bound proposal. If the acknowledgment is lost, an explicit retry reconciles the saved item.

3. 03 · Triage

   Apply configured transitions with revision checks. Preserve human changes and inspect durable mutation evidence.

Verified in synthetic local fixtures through independent HTTP services, post-commit response loss and a target restart. This is downloadable reference source; a visual Kanban board, managed backend and customer workflow acceptance remain open.

Connected reference · Event Relay 0.1

Save the change.
Keep the notification connected.

Every saved Work Items change has a durable event. The relay reads an anchored, tenant-scoped feed and queues the selected metadata in Outbox. It advances its checkpoint only after the destination acknowledges that event. A lost response leaves a recoverable checkpoint and a stable identity.

1. 01 · Commit the intent

   Save the work-item mutation and its event together. Validate the journal and previous event before resuming a feed.

2. 02 · Transfer explicitly

   Queue a bounded page with source and target identity checks. Reuse the same event key after an uncertain acknowledgment.

3. 03 · Keep sending separate

   The relay can queue notifications. An independently authorized operator controls Outbox delivery and receipt reconciliation.

A self-hosted Python reference with fictional local workflow fixtures. It transfers selected event metadata, not Feedback text or media. No background poller, automatic external notification, universal exactly-once guarantee or enterprise admission is implied. Coordinated restore, key migration, HA and customer workload qualification remain separate.

Connected reference · Webhook Outbox 0.1

Queue the handoff.
Know when delivery is uncertain.

Keep a webhook in a durable, tenant-scoped outbox before an operator dispatches it. The host configures the destination and HMAC identity. A cooperating receiver can deduplicate the delivery and report what it accepted, so a lost response can be investigated without blindly sending again.

1. 01 · Queue

   Save the webhook for a host-configured destination. Scoped credentials keep queueing, dispatch and inspection authority explicit.

2. 02 · Send one attempt

   Dispatch explicitly with HMAC identity and record the result. A missing acknowledgment remains uncertain; it does not trigger an automatic retry.

3. 03 · Reconcile

   Ask a cooperating receiver for the stable delivery identity. Inspect the saved evidence before deciding the next action.

A self-hosted Python reference with bounded synthetic receiver fixtures. Receiver deduplication and lookup are required for this recovery profile. It does not establish exactly-once delivery, send client messages or provide a managed notification backend. Customer acceptance and enterprise admission remain separate.

06 · Contracts before composition

Discover once.
Connect through explicit contracts.

A unified catalog can describe many capabilities without giving one credential unlimited authority. Keep an existing provider, bring your own key, use a licensed managed connection or choose a qualified Gradia implementation.

Grow the connections through a versioned adapter registry. The downloadable Ruflo bridge supports registered providers, editions and operations through one gateway, with explicit schemas, permissions and telemetry. Existing workflows pin their contracts; the offline composition planner now identifies affected consumers and stale pins. Runtime consumer qualification and migration remain planned.

# Public discovery, no tenant data or execution authority
curl 'https://www.gradiahq.com/api/blocks/v1/catalog?q=feedback'
curl 'https://www.gradiahq.com/api/blocks/v1/catalog/feedback'
curl 'https://www.gradiahq.com/api/blocks/v1/skills?limit=8&origin=upstream'
curl 'https://www.gradiahq.com/api/blocks/v1/skills/integrate-feedback'
curl 'https://www.gradiahq.com/api/blocks/v1/skills/plan?ids=integrate-feedback,review-block-candidate'

# Separately deployed feedback reference, scoped credential
curl http://127.0.0.1:3191/v1/feedback \
  -H "Authorization: Bearer $FEEDBACK_TOKEN" \
  -H 'Idempotency-Key: keep-this-key-for-reconciliation' \
  -H 'Content-Type: application/json' \
  -d '{"message":"Make the approval status clearer","category":"idea"}'

The reference uses Python/FastAPI and SQLite metadata with selectable database or private-filesystem media storage, plus a TypeScript HTTP client, React widget and Rust telemetry-contract validator. This is not a native implementation in every language. Self-hosted production use requires workload-specific security, retention, deployment, monitoring and recovery qualification.

07 · Admission is a separate decision

Useful code.
Inspectable evidence.
Accountable admission.

The admission prototype binds an artifact to a protocol, independently supplied evidence and operator-controlled reviewer scopes. Missing, stale, failed or skipped required evidence blocks eligibility.

It screens supplied receipts; it does not execute every test or prove their truth. Passing means eligible for review, not automatically admitted, merged or published. Rights, security, behavior, tenant boundaries, telemetry, accessibility, composition and recovery each need their own evidence.