InfraOriginShare a real configuration
Submit Stack on GitHub . A GitHub account is required and your issue, username and attachments are public. Describe the operator, workload, hardware, software, limits and results. Costs and measurements can be unknown. Never post passwords, tokens, SSH keys, production credentials, private IPs, customer information or unredacted bills/logs. We do not need server access.
A human moderator checks sources, permission to publish, and which claims the evidence actually supports. Opening or approving an issue does not publish a page. A moderator prepares structured data, validates it, reviews a change in the private website repository, and publishes through the normal website release process. Submissions never run as code. Payment cannot buy a verification status.
Evidence applies to a claim
Authorship, configuration, cost and performance have separate statuses:
| Status | Meaning |
|---|---|
| Not provided | No reviewed support for this claim. Unknown is not zero. |
| Public-source | A dated public source reports this information. It has not been confirmed by the operator. |
| Owner-confirmed | The operator controls the linked identity and explicitly confirms this particular claim. This is a declaration, not an independent measurement. |
| Evidence-backed | A moderator reviewed material supporting the specific claim and documented what it demonstrates. |
| Independently measured | A named independent reviewer measured the stated result using the linked, reproducible method. |
An ownership claim never upgrades cost or performance automatically. A recognizable name is not technical evidence. Each evidence record includes its scope, source date, review date, reviewer, method and review due date. An expired review stays visible as historical evidence; it is not presented as current. Even current reviews describe a dated snapshot, not continuous monitoring.
For a cost, specify currency, purchase or billing date, location, tax/shipping, included hardware/services, amortization and reporting period where relevant. For performance, specify the workload, configuration/version, input, measurement window, tools and repeatability limits. Do not compare metrics whose contexts differ.
Claim ownership
Claim Ownership with the Stack URL and public profile you control. Publish a link to that issue on an operator-controlled website, repository or profile already linked by the case. The moderator checks the reciprocal link and explicit statement of control. A GitHub username alone is insufficient. Use a redacted, public proof; never send credentials. A successful claim confirms only the scopes explicitly reviewed.
Correct a record
Suggest Correction with the Stack URL, disputed field and a dated public source. A moderator compares the evidence, records the decision and updates the revision history through a private website review. Disputes can leave a claim unknown while evidence is assessed. If sensitive data was accidentally posted, stop sharing it, use GitHub’s removal/reporting controls and rotate exposed credentials; do not repeat them in another issue.
Share and embed
Each published Stack provides its permanent link and a compact iframe card showing all four evidence statuses and any expired reviews. The card links to the evidence ledger, includes a build date and runs no analytics or JavaScript. Share/embed copy events measure successful copies on this site; they do not prove a social post or an external embed was published.
Measuring useful interest
With optional analytics consent, we count Stack views, external arrivals, successful link/embed copies, opening an intake form and choosing an interest such as reproducing a Stack or finding hardware or a provider. No search queries, detailed configurations, full referrer URLs, issue bodies or contact information are sent in these events. Declining or withdrawing consent stops these events for the analytics destination.
Opening a form is not a submitted configuration or ownership claim. Actual submissions and review outcomes are counted from GitHub issues, classified by moderators; spam, duplicates, tests and withdrawals are excluded. The first version does not receive a GitHub submission callback, store sales leads, match providers or create orders. The interest selector records only an optional aggregate signal; it does not promise a reply.