Launch v0.6: permanent public Playground + external distribution

[Videirafo]

Objective

Ship a permanent public URL for the Safe Agent Playground and use the verified demo assets to launch the project externally.

Scope

• Add Render Blueprint for a free FastAPI web service
• Add Deploy to Render entrypoint to README
• Publish canonical onrender.com URL
• Validate /, /health, /docs, /openapi.json, and all five Playground scenarios over the public internet
• Add canonical live-demo link to README
• Add verified screenshot/GIF assets generated from the real application
• Reach Agent Ready 100/100, llms.txt 100/100, and accessibility 100/100
• Launch on Show HN — currently blocked by Hacker News account eligibility (showlim restriction for accounts without sufficient prior HN participation)
• Launch on DEV #showdev
• Share in a Reddit venue that explicitly allows project promotion — published to r/LLMDevs with Discussion flair on 2026-09-07 around 17:17 America/Sao_Paulo
• Publish a LinkedIn engineering post
• Record first identifiable external visitor/use signal
• Record first external feedback — first clear signal: an external reader said the premise was confusing; tracked in feedback: clarify the Safe Agent Playground premise for first-time visitors #31
• Record first external Star / Watch / Fork
• Receive and review first external pull request / contributor

Channel status

• Show HN: project is technically eligible, but the current HN account is temporarily ineligible to submit Show HN because HN is restricting these submissions for accounts without enough prior community participation. Do not attempt to bypass this restriction with alternate accounts or coordinated activity. Revisit after genuine HN participation.
• Reddit: launched successfully in r/LLMDevs with title I built a runnable open-source demo for AI-agent authorization boundaries looking for technical feedback and Discussion flair.
• Additional Reddit discussion: a post/discussion visible in r/learnAIAgents reached 265 views and produced the first actionable external feedback: the premise was confusing. This is now tracked as issue feedback: clarify the Safe Agent Playground premise for first-time visitors #31.

Adoption baseline — after first external feedback, 2026-09-07

• stars: 0
• watchers/subscribers: 0
• forks: 0
• Issue feedback wanted: run the Safe Agent API and report setup friction #17 feedback comments: 0
• Issue good first issue: add a pluggable JSONL audit sink to Safe Agent API #16 good-first-issue comments: 0
• open external PRs: 0
• first external feedback signal: yes — premise clarity
• actionable follow-up issue: feedback: clarify the Safe Agent Playground premise for first-time visitors #31 feedback: clarify the Safe Agent Playground premise for first-time visitors
• Docker joke/comment is not treated as a technical defect without a reproducible report
• repository description: not configured
• repository topics: not configured
• repository homepage: not configured
• Discussions: disabled

Adoption loop

distribute → measure visits → observe drop-off → collect feedback → fix real friction → attract contributor → review external PR → merge → document learning → repeat

First-loop success criteria

• 1 external user actually tries the Playground;
• 1 external feedback signal — achieved;
• 1 real external contribution.

Stars, Watchers and Forks are tracked as secondary adoption signals, not artificially optimized.

Constraints

• GitHub repository remains the source of truth.
• No new source repository for hosting.
• No secrets, database, or LLM provider required.
• No artificial stars, watchers, votes, or engagement farming.
• Do not mix deployment with MarcaIA or unrelated Netlify projects.

[Videirafo]

Progress update — 2026-09-07

Completed:

• ✅ PR ci: generate verified Playground demo assets #20 merged: verified Playground screenshot + GIF generated from the real FastAPI app via Playwright/Pillow and displayed in README.
• ✅ PR chore: prepare permanent Render deployment #23 merged: render.yaml Free web-service Blueprint, /health deployment contract, Render Blueprint CI validation, deploy guide, and external launch kit.
• ✅ Render Blueprint / Docs Quality / CodeQL all passed before merge.
• ✅ Launch channels verified: Show HN requires a directly usable project; DEV #showdev accepts project launches; r/LLMDevs explicitly allows free open-source project sharing.

Pending external authorization:

• ⏳ Connect Render account/app so the canonical onrender.com service can be created.
• ⏳ After deploy: internet smoke test /, /health, /docs, and the five Playground scenarios.
• ⏳ Add the verified live URL to README/profile and replace {LIVE_URL} in docs/LAUNCH.md.
• ⏳ Publish launch posts from authenticated HN / DEV / Reddit / LinkedIn accounts.

No artificial stars, watchers, votes, or engagement will be used.

[Videirafo]

v0.6 launch gate update

Permanent public URL is live: https://safe-agent-playground.onrender.com/

Completed:

• ✅ Render Free Web Service created from the canonical GitHub repository
• ✅ Render reports deployment dep-dafgfntbedkc73959qog live from SHA a55b8ed750ae5dd337bf777ba066972c88786de6
• ✅ External scanner confirmed HTTPS + HTTP 200 on the Playground and discovered /openapi.json
• ✅ Accessibility scan: 100%
• ✅ PR docs: publish canonical live demo #24 added canonical LIVE DEMO links and the real URL to docs/LAUNCH.md
• ✅ Live Demo Smoke passed from GitHub Actions against the public internet
• ✅ /, /health, /docs, /openapi.json passed
• ✅ all five public POST /v1/run-demo scenarios passed against the real Render deployment
• ✅ Docs Quality passed
• ✅ CodeQL Security passed
• ✅ PR docs: publish canonical live demo #24 squash-merged as 0c17a00b5372f424cdd964835b2a6a10d49b6220

Next distribution gates:

• Show HN
• DEV #showdev
• one Reddit community that permits free/open-source project sharing
• LinkedIn engineering post
• track first external feedback / Star / Watch / Fork / contributor

Non-blocking discovery backlog from the public agent-readability scan: add llms.txt, robots.txt, sitemap, canonical/meta/OG/JSON-LD and a markdown mirror.

[Videirafo]

Discovery hardening completed before external launch

PR #26 was merged after all 4 gates passed: Docs Quality, Example Safe Agent API, Verified Demo Assets and CodeQL Security.

Render deployment dep-dafglhuq1p3s73blsnk0 promoted SHA b17552622273baaf6b5e1799252502cbfb3aea2c and is live at the same canonical URL.

External re-scan after deployment:

• agent-readability: 30 → 45
• llms.txt: 0 → 100
• accessibility: 100 → 100
• Site discovery checks: 13/15 passed
• HTTPS, robots.txt, llms.txt, llms-full.txt, sitemap.xml, sitemap.md, AGENTS.md and root OpenAPI are now discoverable.

Remaining scan improvements (non-blocking): sitemap <lastmod>, stronger AGENTS.md usage sections, and per-page markdown/content-negotiation refinements.

The project is ready for the human distribution phase.

[Videirafo]

Technical launch gate is now fully closed.

Public Safe Agent Playground status:

• canonical URL live: https://safe-agent-playground.onrender.com
• Render production SHA: 107b4173ef53f066dd4edac7e49f62dd9be9e450
• Agent Ready: 100/100 — Excellent
• Site: 15/15
• Page: 25/25
• llms.txt: 100/100
• Accessibility: 100/100
• percentile: 99 of 1,638 sites
• README includes verified screenshot/GIF and live demo entrypoint
• public feedback and good-first-issue paths are already available

From this point, the remaining launch work is distribution and external adoption: visitors → feedback → Star/Watch/Fork → external issue → external PR → contributor.

[Videirafo]

Adoption baseline before external distribution

Technical launch gate is complete and the public demo is live at https://safe-agent-playground.onrender.com with Agent Ready 100/100.

Baseline at start of distribution:

• Stars: 0
• Watchers/subscribers: 0
• Forks: 0
• Issue feedback wanted: run the Safe Agent API and report setup friction #17 external feedback comments: 0
• Issue good first issue: add a pluggable JSONL audit sink to Safe Agent API #16 good-first-issue comments: 0

Primary conversion goals for the first cycle:

1. one external user runs the Playground;
2. one external feedback signal is captured;
3. one external contribution reaches a reviewable PR.

Secondary signals: first Star, Watch/subscription, and Fork.

Do not optimize for vanity metrics or artificial activity. Measure channel -> visit -> feedback/contribution and document what actually converts.

[Videirafo]

Distribution order — first adoption loop

1. Show HN — primary launch. The Playground is directly usable without signup/API key and is ready for technical feedback.
2. r/LLMDevs — preferred Reddit venue for this first round because the community explicitly permits free open-source project sharing without prior moderator approval.
3. DEV #showdev — project-launch post using the verified GIF/screenshot and a community-driven write-up.
4. LinkedIn — engineering narrative focused on model suggestion != authorization, not a generic promotional post.

Hold for later

• r/LocalLLaMA: do not use as the first Reddit launch unless the author's account already satisfies the community's meaningful-participation/self-promotion ratio. Avoid risking removal before we have baseline distribution evidence.

Conversion CTA

Primary: try the live Playground and identify one unclear authorization boundary.
Secondary: report setup/use friction in #17.
Contributor CTA: take #16 (good first issue) if the JSONL audit-sink scope is interesting.

Measurement

After each channel, record: attributable traffic if available, stars, watchers/subscribers, forks, #17 comments, new issues, and external PRs. Do not change product behavior unless feedback identifies real friction.