Welcome 👋 start here: how these Discussions are organized

[senamakel]

Welcome. This is where OpenCompany gets worked out in public: how to run a company with a headcount of one, what breaks when you try it, and what gets built next.

Discussions here are sorted by what you are doing, not by what kind of post you are writing. Find the row that matches your situation. Each category opens with a short form that asks for the evidence which usually settles the thread on the first reply.

Where things go

You have	Category
A question about setting up or running a company: company.toml, roles, approvals, workflows	Running a company
An agent or a run that did the wrong thing, stalled, or ignored steering	Agents and Runs
Anything about backends, data directories, tenancy, exports or bundles	Storage and Tenancy
Any other question	Q&A
A change big enough to break someone already running this	RFCs
A company you are actually running on OpenCompany	Show your company

Reproducible behavior that should change belongs in an issue rather than here. If a discussion turns out to be a bug, a maintainer opens the issue and links it, so you never have to file the same thing twice. A vulnerability goes through the security policy and never into a public thread.

Getting answered quickly

The form asks for your version, how you are running it (cargo, Docker, hosted), the container log, the run's journal, and whichever slice of company.toml is involved. Filling that in is faster than the three replies that would otherwise ask for it one field at a time.

Redact before you paste. A discussion is public and indexed by search engines, and editing it afterwards does not un-publish a key. Once a credential is in a post, you have to rotate it.

Then mark the answer when you get one. In the Q&A-style categories that marker is the whole mechanism by which your thread becomes the next person's documentation. Leave it unmarked and somebody asks the same question next week.

What happens on our side

Maintainers work a queue rather than an inbox. A thread that has replies but none from a maintainer gets labelled awaiting maintainer, and those get worked oldest first. That label exists because the built-in "unanswered" filter cannot see the case that actually matters: four people tried to help, and nobody with commit access ever turned up.

Old threads stay open. An answered one is documentation.

SUPPORT.md has the full routing table. docs/community/discussions.md has the triage rules and every label we use, so you can tell where your thread currently sits.

About OpenHuman

OpenHuman is the runtime inside OpenCompany, so questions about the launcher, the agent journal, or the workspace root really do belong to both projects at once. Post where you hit the problem and link the other repository instead of closing either one as a duplicate. They have different maintainers, and the link is what keeps both able to answer.

Introduce yourself

If you have just arrived, reply here with what you are trying to run and where you are stuck. That is a fine first post, and people tend to answer it.