SGUILD.com is where people act. It gives The Solar Guild a place to define Objectives, divide work into smaller steps, form Teams and Charters, submit results, receive review, and preserve what happened.
The platform already has substantial machinery. The near-term job is not to add every imaginable feature. It is to make one bounded next action obvious and demonstrate value for a named user.
Contents (5 sections)
The main building blocks
Supported by cited sources| Building block | Simple meaning |
|---|---|
| Objective | A specific desired result with ownership, evidence, and an end condition |
| Quest | A bounded self-directed or collaborative learning activity with evidence |
| Opening | A role, task, project, or partnership with stated terms |
| Artifact | A piece of work that another person can inspect |
| Review | A human judgment about specific work under stated criteria |
| Team | A capability network with highly selective admission and non-mutually exclusive membership; joining one does not prevent joining another |
| Charter | A community connected by a durable commonality and written agreement |
| Garden | A durable venture, service, program, organization, or operating institution |
The first-use rule
Active workA visitor should not have to understand every word above. The first screen should show one bounded action they can complete now and the next move that completion unlocks. Deeper structure should appear only when it helps that action.
Evidence must advance by explicit states
Proposed- Artifact-backed: an inspectable result exists.
- Reviewed: an accountable human assessed it against stated criteria.
- Sponsor-verified: the owner of a concrete need confirmed the contribution or acceptance.
- Outcome-confirmed: evidence shows adoption or another documented result.
- Self-submission and AI feedback never create human-reviewed, sponsor-verified, or outcome-confirmed status.
What a platform record can and cannot show
Active work- A submitted artifact can show that a piece of work was recorded.
- A review can show what a named reviewer concluded within a stated scope.
- An organization response can show whether the work was accepted, used, changed, declined, or left unresolved.
- None of these automatically proves universal ability, authorship, character, or future job performance.
Design rules
Proposed- Ask only for information needed for the current Objective.
- Show terms before commitment.
- Keep private worker support separate from employer-facing activity.
- Make corrections and disagreements visible when they affect a record.
- Do not let points, badges, payment, or early arrival buy authority.
- Require identity and organization verification before a public organization proposal or scoped Objective; verification still does not guarantee quality, fit, safety, or an outcome.
- Keep Quests focused on learning; do not use them as a euphemism for unpaid commercial work.
- Use existing services when they solve the need better.
References and limits
This page is published by The Solar Guild. Sources are listed so readers can inspect the basis of the page. A project statement is not independent proof unless the page identifies supporting outside evidence.
- Direct review of SGUILD.com routes and product objects
- Current platform and evidence rules of The Solar Guild