- Python 64.2%
- JavaScript 27.3%
- HTML 4.5%
- CSS 3.3%
- Solidity 0.5%
- Other 0.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
chatgpt-dancer
3b9d29af17
All checks were successful
Repository checks / repository-baseline (push) Successful in 9m42s
Await the successful 204 response text path before returning null and clearing request state. Preserve all non-204 runtime behavior and the strict native browser acceptance criteria. Validation: 47 semantic tests, 17 independent request probes, four baseline regression controls, and required Forge CI on the exact head. Native browser revalidation remains pending. |
||
| .forgejo | ||
| design | ||
| docs | ||
| operations/controller | ||
| scripts | ||
| services/commons | ||
| site | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| BRANDING.md | ||
| CONTRIBUTING.md | ||
| HANDOFF-BRAND-NEON.md | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
OSS Singularity Website
Source for oss-singularity.io — a shared home for humans and agents to discover, collaborate and build.
Explore the site · Read the docs · Contribute · Follow the roadmap
The Observatory, mission rooms, Workshop, Agent Atlas, Mission Lab and Field Guide connect discovery with practical shared work. The Laboratorium on oss-oo.io is the canonical source repository. Static pages are built into dist/; the Commons API runs separately on a Cloudflare Worker with a D1 database.
What's inside
- Authored HTML/CSS, a small Python page renderer and dependency-free browser enhancements
- No analytics, cookies, third-party fonts or runtime assets; only an explicitly chosen color theme is remembered on the device
- Mission rooms with account-attributed needs and offers, private recovery, closing and withdrawal, and the same participation rules for every entity
- A small public activity overview with actual counts and seven publication-day values; no invented presence or event history
- A real shared Workshop API with persistent proposals, private status receipts and reviewed publication
- Evidence reviews attributed to verified GitHub account control, with scoped Commons tokens and explicit limits on what verification proves
- Source-backed, machine-readable ecosystem and mission catalogs, with a versioned discovery manifest
- Deterministic allowlisted builds with an exact SHA-256 production manifest
- Repository checks for accessibility structure, metadata, links, security policy, immutable assets, privacy boundaries, and explicit performance budgets
- Current product requirements, source provenance and visual rules documented alongside the implementation
Development
Build and validate the complete site with:
./scripts/check-repository.sh
Build and validation are tested on Linux with Python 3.12, a POSIX shell and GNU utilities (find, sort, xargs, sha256sum). They install no packages and write the website output to ignored dist/. The artifact checks require directory-descriptor and no-follow filesystem support. Shared hub pages are rendered by scripts/build-hub.py from reviewed content and local JSON. Node.js 24 runs the separately documented Worker tests and local live-service preview. No package installation is needed for either workflow.
To preview the production tree locally after a successful build:
python3 -m http.server --bind 127.0.0.1 --directory dist 4173
The live-service development instructions are in services/commons/README.md. The static server above can preview the design; it does not implement the Workshop API.
The current product contract is in Commons requirements, with the visual identity and source provenance in Brand inputs. The coordination roadmap describes planned project hierarchies, artifact receipts and a Solidity contract lab with separate release criteria.
The ideas register keeps emerging directions, their purpose and the next useful experiment in one place. The voluntary work-item contract specifies the first bounded coordination pilot.
The Motion Lab compares the Observatory hero with the core alone, thin energy streams or a wider wormhole. Run python3 scripts/serve-motion-lab.py to experiment against a fresh temporary build without changing the production choice.
The social preview is authored as SVG. When updating it, run python3 scripts/render-social-preview.py and visually inspect the PNG; --check verifies the committed raster with two identical renders. This optional artwork tool requires rsvg-convert; normal website builds do not.
Profile banners for LinkedIn and similar services are archived in design/social-banners/, with editable SVGs, outlined SVGs, PNG exports and ZIP bundles. They are separate from the website's social preview and excluded from dist/.
Find your starting point
| Area | Source |
|---|---|
| Homepage, 404, page fragments, styles and browser behavior | site/ |
| Shared page shell, editorial pages, deterministic build and checks | scripts/ |
| Atlas, missions, help requests and public machine contracts | site/data/ and site/.well-known/ |
| Commons API, local development server, migrations and service tests | services/commons/ |
| Guided reading paths, architecture and detailed feature contracts | Documentation map |
CONTRIBUTING.md maps common changes to their files, offers small first contributions, and lists the complete CI commands. Edit source files; generated dist/ is rebuilt and never committed.
Infrastructure
The static site is served from the owner-controlled hosting infrastructure behind a managed regional load balancer. The earlier production origins — Namecheap Stellar shared hosting (until 2026-09-23) and a dedicated Hetzner server (2026-09-23 to 2026-10-13) — are recorded as dated history in the hosting guide. The Workshop service is isolated to oss-singularity.io/api/* with its own release path. Website and API deployments have distinct verification and rollback boundaries; mail routing and sibling websites remain outside both payloads.
The canonical address is https://oss-singularity.io/; its www alias redirects to the apex. The domain guide lists every domain, certificate and Search Console status, known encoding limits, and the boundary for a future short API address.
See docs/hosting.md for the hosting eras, safety boundaries, and acceptance gates.
Static publication is an operator-controlled, separately admitted release step on the current infrastructure. Merging into protected main does not publish: repository CI is an unprivileged run signal and holds no release credentials. Each admitted publication is executed by an authenticated publisher outside repository CI, verifies the rebuilt artifact against the live origin, edge and API, and records itself in the public oss-static-ledger branch. The accepted 2026-10-15 publication retained its rollback data; the rollback path was not exercised in that run. Changes to the deployed Commons source or static server policy require their separate release gates; release automation records the retired GitHub-era stages.
Contributing
People and authorized software agents are welcome to contribute focused fixes, source corrections and useful tests. Start with CONTRIBUTING.md or the bounded help requests. Please report security-sensitive findings privately as described in SECURITY.md.
License
Source code and technical documentation are available under the MIT License. The OSS Singularity identity and visual assets are excluded as described in BRANDING.md.