Proposal: AINative Studio as a gstack host — agent memory, vector DB, and MCP tools for gstack users #891

Context

We're the team behind AINative Studio — an AI agent infrastructure platform (ZeroDB, ZeroMemory, Agent Cloud, MCP servers). We recently submitted PR #850 adding AINative as a gstack host with 5 domain skills, which was closed without review. Totally understand — adding a new host is an architectural decision that deserves discussion first.

What We're Proposing

1. AINative as a gstack host (hosts/ainative.ts)

AINative runs on Claude Code (same runtime as the claude host) but enforces platform-specific rules:

• Zero-tolerance for AI attribution in commits (requires the coAuthorTrailer: '' fix we submitted in the same PR — discovered a bug where || should be ?? in resolvers/utility.ts:372)
• Mandatory TDD with 80% coverage
• File placement rules
• Issue tracking enforcement

2. Five domain skills that give gstack users access to agent infrastructure

Why This Makes Sense for gstack

gstack gives developers workflow infrastructure (how to plan, review, ship). AINative gives agents persistent memory and tools. Together:

• A gstack user running /qa could use ZeroMemory to persist test results across sessions
• /learn operational learnings could sync to ZeroDB for semantic search across projects
• /office-hours planning sessions could store decisions in the knowledge graph
• Any gstack skill could call ZeroDB MCP tools for persistent storage

The skills are reference docs (no $B commands, no templates) — zero maintenance burden on the gstack team.

What We've Already Done

We also submitted 5 bug fix PRs to build contributor credibility:

• Fix cookie-import path validation bypass + hardcoded /tmp #852 — Security: cookie-import path validation bypass (224 tests pass)
• Fix CDPATH breaking all bin/ scripts + fragile JSON stripping via sed #853 — CDPATH fix across 23 shell scripts + fragile JSON stripping
• Remove redundant chmod -R on /tmp + avoid body buffering for response size #854 — Docker chmod -R fix + response body buffering perf
• Add .ainative/ to .gitignore for host output #855 — .gitignore for host output dirs
• Add uninstall link to install section + NO FINDINGS sanity check #856 — Uninstall docs + NO FINDINGS sanity check

Questions for Maintainers

1. Is the gstack host system open to third-party platforms, or only hosts the core team maintains?
2. If third-party hosts aren't accepted, would the 5 skills be accepted as standalone community skills (without the host config)?
3. Any feedback on the coAuthorTrailer bug fix (|| → ??) — should that be a separate PR?

Happy to adjust the approach based on your guidance.

— urbantech / AINative Studio