❓ Traylinx FAQ: Launching the Network¶
Status: Living Document | Last Updated: 2025-12-08
This document captures key strategic questions and answers about launching the Traylinx Agent Network.
🚀 Getting Started (The "Day 1" MVP)¶
Q: Do we have everything we need to start right now?¶
A: You have the Engine (Infrastructure), but you are missing the Keys (Onboarding). Technically, the network runs perfectly. Functionally, outside developers cannot "enter" yet.
Q: What is strictly missing to have a first working system?¶
A: You are missing exactly two small "glue" components:
1. Credential Vending Machine: A way to generate client_id / client_secret pairs for new developers (currently manual DB entry).
2. Publisher Tool: A simple CLI to read a traylinx-agent.yaml file and register it. Currently, developers would have to hand-craft complex JSON requests, which is error-prone.
Q: Do we need the full Store (Billing, UI, etc.) to start?¶
A: NO. You do not need the Marketplace UI, Billing System, or Developer Portal to launch the "Minimum Viable Network". You can start with a "CLI-first" approach.
Q: What is the "Alien" Strategy for a fast start?¶
A: Focus on the 10% User Experience layer that unlocks the 90% Engineering you've already built:
1. Define the Standard: Lock down the traylinx-agent.yaml schema.
2. Build the CLI: Create a tiny traylinx tool with:
* login: Saves credentials.
* publish: Reads YAML -> Validates -> Registers agent.
🛠️ Technical Implementation¶
Q: How does an agent join the network?¶
A: Technical flow:
1. Registration: Agent calls POST /a2a/registry/register on the Registry Service.
2. Validation: Registry validates identity via Sentinel (A2A Auth).
3. Discovery: Once registered, the agent immediately appears in POST /a2a/registry/discover results for any other agent to find.
Q: How do we solve the "Credential Vending" problem for Day 1?¶
A:
* Day 1 (Manual/Admin): We create a simple admin script (scripts/create_developer_credentials.py) that you run to generate keys for pilot partners.
* Day 30 (Self-Service): We build the Developer Portal where they sign up with GitHub/Google and get keys automatically.