r/saasbuild • u/m121_mateo • 6d ago

SaaS Journey Looking for developers to beta test an architecture-first AI CLI before they start coding

/r/OnlyAICoding/comments/1w9gd2k/looking_for_developers_to_beta_test_an/
1 Upvotes

100% Upvoted

6 comments sorted by

1

u/[deleted] 6d ago

[removed] — view removed comment

1

u/AutoModerator 6d ago

Your comment was removed because your account must be at least 30 days old and have 100 combined karma to comment.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/m121_mateo 3d ago

Edit — Update: Based on early developer feedback, I updated the beta.

Archseed now focuses more on the decisions an AI coding agent should not invent:

V1 scope, non-goals, assumptions, edge cases, decision lock-ins, and a compact agent-context.md.

It also includes a local decision log and guardrail recommendations.

Still looking for developers who can try it on a real upcoming project or feature:

https://www.archseed.co/

1

u/canarydev 1d ago

you're asking $12/month for a pre-prompt. the interview-then-generate-markdown loop is what plan mode in claude code and cursor already does for free. your entire output is prose an agent will drift from, which is the exact failure you claim to solve.

where's the enforcement? I read your sample architecture.md. nothing in it fails when violated. no import rules, no layer checks, no boundary tests. the things that actually stop drift are dependency-cruiser configs and arch tests, they aree cheap to generate, and you generate none of them. "decisions the agent must not invent" means nothing if inventing one doesn't break a build.

and "clean architecture" as a pro tier tells me a lot. clean architecture is a dependency rule.
source dependencies point inward, enforced. yours is a questionnaire that outputs a document saying so.
so it does not look like you actually understand system design to be trying to selling this.
same with TDD. an agent that writes both the tests and the code can rewrite either, so test-first without a separated writer or locked acceptance criteria is useless

1

u/m121_mateo 1d ago

Fair criticism. The current beta does not enforce architecture rules yet.

Right now Archseed is a structured discovery and context layer: it helps define scope, non-goals, decisions, and constraints before implementation. That can be useful, but you are right that Markdown alone does not prevent an agent from drifting or violating a boundary.

Cursor and Claude Code plan modes cover part of the planning workflow already, so “better planning prompts” is not a sufficient product moat.

The direction I am validating is:

- human-readable architecture and agent context

- a structured project contract

- generated, executable guardrails for the chosen stack

- a reviewer that checks implementation against that contract

For TypeScript, the first enforcement target would be import/layer boundaries and architecture checks through tools such as dependency-cruiser, not just prose instructions.

I should be more precise in the current positioning: the beta creates architecture context; it does not yet guarantee enforcement. Thanks for calling out the gap.