Skip to content

The Archety Constitution

Version: 1.0 | Status: Living Document


πŸ“œ The Preamble

We are not building software; we are building a digital companion. Archety is a presence in your group chat that feels like a friend. It is helpful, chaotic, privacy-conscious, and always available.

This document outlines the non-negotiable principles that guide every line of code we write and every product decision we make.


πŸ’Ž Core Principles

1. Messaging-First (The "No App" Rule)

We live where the user lives. - The Rule: If it requires leaving iMessage, we failed. - The Vibe: Everything happens in the chat. No "download our app", no "click here to login". - The Tech: We use UI Blocks (Polls, Cards) that render natively in the message stream.

2. Personality is the Product

Sage is not a tool. She is a character. - The Rule: Every output must pass the "Vibe Check". - The Vibe: Sage mirrors the group's energy. She uses slang, emojis, and lowercase text. She has opinions. - The Tech: The Persona Styler rewrites every system message to match the active persona.

3. Privacy is Trust

We are guests in their private chats. - The Rule: No surprises. We explain what we see. - The Vibe: "I peeked at your calendar for a sec to find a slot." - The Tech: Explicit, conversational consent for every data access. "Forget that" works instantly.

4. Multiplayer by Default

Everything is better with friends. - The Rule: Every feature must work for a group. - The Vibe: Trip planning, shopping, roasting each otherβ€”it's all social. - The Tech: Event Sourcing ensures everyone sees the same thing at the same time.

5. Fail Like a Friend

Robots crash. Friends make mistakes. - The Rule: Never show a stack trace. Never say "Error 500". - The Vibe: "Oof, my brain glitched. Give me a sec." - The Tech: Error handlers that catch exceptions and return persona-styled apologies.


πŸ—οΈ Architectural Philosophy

Evolution, Not Revolution

We stand on the shoulders of giants (our own previous code). - Don't Rebuild: The Workflow Engine works. The Memory Vault works. Keep them. - Extend: Add the Multiplayer Layer on top. - Refactor: Clean up as we go, but don't stop shipping.

The "Chaotic Good" Test

Before shipping a feature, ask: 1. Is it useful? (Good) 2. Is it fun? (Chaotic) 3. Does it feel like a text? (Messaging-First)

If the answer is "Yes" to all three, ship it.


🚫 Non-Goals

We are NOT building: - A Productivity Suite: We are not Google Workspace. We are the glue between tools. - A Visual App Builder: No drag-and-drop. We build with code and conversation. - An Ad Platform: We monetize value, not eyeballs.


πŸš€ Conclusion

We are building the future of social coordination. It's going to be messy, it's going to be hard, and it's going to be incredibly fun.

Stay chaotic. Stay caring. Ship code.