Skip to content

submit io.telepat.ideon-free v0.3.1#16

Open
andreimarinescu wants to merge 1 commit into
pilot-protocol:mainfrom
telepat-io:submit-io.telepat.ideon-free-v0.3.1
Open

submit io.telepat.ideon-free v0.3.1#16
andreimarinescu wants to merge 1 commit into
pilot-protocol:mainfrom
telepat-io:submit-io.telepat.ideon-free-v0.3.1

Conversation

@andreimarinescu

Copy link
Copy Markdown

App submission

App id: io.telepat.ideon-free
Version: 0.3.1
Publisher: ed25519:5cqj+zTVecj8r0YRUShpgFi/g7TxDg1lkDKQzfNyDyc= (will be added to pilot-protocol/catalog publishers/registry.json)

Automated gate

  • submission-validate CI is green (bundle sha, manifest valid + signed, <ns>.help, id/version).

Maintainer checklist (SPEC §7.2 — do not merge until all checked)

  • Publisher identity is known / added to the registry.
  • Grants are proportional to the described function. Scrutinize any
    proc.exec, fs.write, key.sign, or broad net.dial target.
  • submission.json description accurately reflects the app.
  • Backend host (for net.dial) is one the publisher controls.

On merge, automation releases the bundle on pilot-protocol/catalog and opens
the catalogue index PR on TeoSlayer/pilotprotocol.


Submitter notes (Telepat)

Hello from the Telepat.io team. io.telepat.ideon-free is long-form article
generation for agents: ideon-free.generate(idea) returns a job id,
ideon-free.poll(jobId) returns the finished markdown, and ideon-free.help lists
the methods. It's a thin adapter over our own hosted Ideon backend — no payment, no
per-user keys.

Context for the checklist above:

  • Publisher identity / registry. We're a new publisher, so we'd need an entry in publishers/registry.json:
    { "pubkey": "ed25519:5cqj+zTVecj8r0YRUShpgFi/g7TxDg1lkDKQzfNyDyc=",
      "name": "Telepat", "contact": "andrei@telepat.io", "apps": ["io.telepat.ideon-free"] }
  • Grants. Just audit.log and a rate-limited net.dial to ideon-mcp.telepat.io. No proc.exec, fs.write, or key.sign.
  • Description. The submission.json description matches what the app does (the three methods above).
  • Backend host. ideon-mcp.telepat.io is operated by Telepat. The app calls it over HTTPS and reads the generated article back over an authenticated route, so it installs and runs on any daemon with no shared filesystem — tested end to end against the live backend. The bundle ships with a default token for that backend so installs are zero-config; it isn't a user secret and only ever reaches our endpoint, scoped by that single net.dial grant.
  • Gate. We ran pilot-app verify on the bundle locally (built from this repo) and everything checks out; we'll tick the box once submission-validate confirms on the PR.

One thing we'd love down the line: the managed-key broker in docs/MANAGED-KEY.md (the
managed-backend-flag work) is exactly the model we'd want — one key held by Pilot, a
keyless adapter, metered per user. We'd happily move this app onto it and be an early
test once it lands on main.

Thanks for building this - we're looking forward to meeting the Pilot network agents!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant