FIELD / 07 · SOURCE CODE, LICENCES & PROVENANCE
Open code.
Clear boundaries.
The Open Source Project is a name for an open workbench. It also includes something concretely open source: this microsite's static HTML, CSS and JavaScript, shared under the MIT licence.
What is actually open source here?
The implementation code of this specific microsite—its HTML page templates and markup structure, stylesheets, JavaScript behaviour and original technical assets—is released under the MIT License, permitting use, modification and redistribution subject to the notice requirements. You can examine the site through View Source or download the corresponding source archive below.
Inspect it. Adapt it. Improve it.
Includes editable HTML, CSS, JS, metadata, licence notices, build documentation and the original technical assets. No account required.
Download microsite source (.zip) ↓Read the MIT licence →What is not granted a blanket open-source licence?
The original editorial prose, essays, research proposals, photographs, brand names and linked Sahilverse projects remain subject to their existing owners' rights unless individually and explicitly licensed otherwise. Public access means they can be read; it does not automatically convey permission to republish or commercialise them.
Research papers and institutional resources linked on the site remain the intellectual property of their respective authors or publishers. Attribution is required where applicable and never implies that those authors endorse this project.
Why the distinction matters
The Open Source Initiative's definition ↗ applies to software distributed on terms permitting redistribution and modifications, among other criteria. A free-to-read essay can be described as publicly accessible, but not automatically as open-source software. A repository without a suitable licence is not automatically open source either.
How to contribute without a public repository
This initial release doesn't claim to have a public issue tracker, contributor organisation or community governance. Download the source, identify a concrete change, and email a description or patch. If a shared repository is later created, it can be linked here after it actually exists.
For substantive editorial or research collaboration, authorship, review, reuse and publication arrangements should be agreed separately. The source-code licence does not authorise re-use of private correspondence or personal information.
No scientific peer review, empirical trial, university affiliation or recognised open-source project foundation is implied. The goal is inspectability and the possibility of constructive contact.