{"contributing.556e154110":"Full-time roles across engineering and product. Remote-first within the EU.","contributing.4de966a2be":"Open positions","contributing.68d70e596c":"Careers","contributing.contact.category":"Contact","contributing.contact.title":"Ask about the release","contributing.contact.description":"Ask which project route, licence, and contribution terms apply before you send work.","contributing.6b8019c889":"Release notes, deep dives, and honest postmortems from the team.","contributing.7dc7ad63ef":"Engineering blog","contributing.0b9d2b2362":"Blog","contributing.a8de6a5d39":"API references, integration guides, and architecture documentation.","contributing.d82fe3b091":"Technical documentation","contributing.9e9cf3221a":"Documentation","contributing.8388910ed9":"Dweve’s technical foundations, from Numerus and BitWeave to Lattice and AION. Check each project’s access route before you begin.","contributing.92c9c7183b":"Browse the foundations","contributing.6cc3364a24":"Foundations","contributing.d5d6e83bf2":"Continue exploring","contributing.d4a046c345":"What next","contributing.2d82a4b27a":"Contributing","contributing.650fabe787":"Open Source","contributing.d4a74b503a":"Read the docs","contributing.ed0515004e":"Clone HEDL on GitHub","contributing.d6c3785735":"Once a project has published, follow its repository instructions to propose a pull request. Before that, the project page carries its round and the terms explain the review route. You can ask about it at any point.","contributing.c5228e1a90":"Submit your first PR.","contributing.90e40d5043":"Get started","contributing.54807a4719":"Accepted changes are merged according to the project policy.","contributing.9a0f39a9d5":"Project policy applies.","contributing.1e0d71f7c2":"MERGE","contributing.b23c53a13f":"Run the CI checks that the project documents for this change.","contributing.4dbe453442":"Documented checks apply.","contributing.13844228ea":"CI","contributing.dbad848f1d":"Address the feedback and follow the project's approval rules.","contributing.d383dcd293":"Address feedback.","contributing.ed6912ad70":"REVIEW","contributing.33eaa0f05a":"Open a pull request when the project accepts one, reference the issue if required, and complete its template.","contributing.9aa7ffc2f0":"Open a pull request.","contributing.55af20415e":"PR","contributing.0fad636e04":"Run the tests and quality checks documented by the project before opening a pull request.","contributing.5043b39eba":"Run quality checks locally.","contributing.984816fd32":"TEST","contributing.5b4fb619bb":"Sign commits and follow the commit format only when the project requires it.","contributing.910bc92e21":"Follow the project's commit rules.","contributing.17e4d77388":"COMMIT","contributing.3af432e996":"Create a branch according to the project's naming instructions.","contributing.a1c514e7cf":"Create a feature branch.","contributing.64c87bd9e1":"BRANCH","contributing.87f29b55c7":"If the project is public and accepts changes, create a fork as its instructions describe.","contributing.0c9f8acad8":"Create a personal fork.","contributing.b477751d76":"FORK","contributing.c69da88167":"Each step has a clear expectation. Use the quality checks the project documents.","contributing.a96d80ffdd":"From access request or fork to review.","contributing.1c0924019c":"Workflow steps","contributing.1ceee7bb3b":"Public projects may use a GitHub fork-and-pull workflow. Check each project's instructions for branch names, commit signing, issue references, review steps and response expectations.","contributing.04cdc5ec81":"Access, branch, review, merge. Each project documents its route.","contributing.e449c5188b":"Submission workflow","contributing.e1f5127329":"Follow the project's documentation requirements for public APIs, examples and longer guides. Add enough context for another contributor to understand and check the change.","contributing.6c2b26374e":"Rustdoc and mdBook.","contributing.96cc00d758":"DOCUMENTATION","contributing.bedff3fc44":"For performance-sensitive changes, include benchmark context when the project asks for it. Record the method, baseline, hardware and observed result so a reviewer can interpret the claim.","contributing.7b63cb3e9c":"Measure before and after.","contributing.82587c5990":"BENCHMARKS","contributing.ad3c8db626":"Add tests appropriate to the change and follow the project's checks for unit, integration, property-based or fuzz testing. Describe any coverage or environment limits that affect the review.","contributing.8616ecdf84":"Unit, integration, and property tests.","contributing.cb73eb0155":"TESTING","contributing.0cc9f02c08":"Quality gates documented for the project and the change.","contributing.95dacde4d0":"Tests, benchmarks and documentation.","contributing.aaca96a0b0":"Quality gates","contributing.2f0c2ff015":"A contribution should carry evidence that matches its change. Follow the project's documented tests, benchmark expectations and documentation requirements; they vary by project and access route.","contributing.f9d85e2220":"Use the testing, benchmark and documentation checks the project requires.","contributing.b610d1070a":"Code standards","contributing.7a7f92d06b":"For native development, use the system dependencies and platforms documented by the project. Some projects provide BUILD.md instructions; check them before you start.","contributing.b494cb8e4d":"Native setup.","contributing.9be34046ca":"LOCAL","contributing.5c973ca059":"Where a project provides a container workflow, follow its Docker or Podman instructions and use the image and commands it documents. Do not assume the container matches CI without checking the project record.","contributing.16318d5f0b":"Container builds.","contributing.8337282975":"DOCKER","contributing.3a8ad29abc":"If the project uses Rust, install the toolchain and components named in its build instructions. Requirements such as rustfmt, clippy, miri or an MSRV are project-specific.","contributing.780d8234f4":"Toolchain and components.","contributing.d59ed14bf9":"RUST","contributing.6cb9935c63":"Ways to prepare a development environment. Check the project instructions for the supported path.","contributing.1b106380b9":"Toolchain, containers, and native setup.","contributing.a97f2d69ec":"Required tools","contributing.a45a0ec144":"The standard path depends on the project. Read its access and build instructions, prepare the documented environment, run the checks that apply, and use the stated review route.","contributing.12ee79bd73":"Many Dweve projects use Rust, but toolchains, minimum versions, containers and integration targets are project-specific. Use the current project documentation as the source of truth.","contributing.805f515086":"Rust toolchain, Docker and local setup where documented.","contributing.e99a087024":"Development environment","contributing.d8899e8b45":"Maintainer review where required","contributing.e29a79fe0c":"Review","contributing.39540900bb":"GitHub Actions","contributing.865abb4fb9":"rustdoc, mdBook","contributing.68a4194227":"Docs","contributing.a314811fbc":"Project test, Miri, and fuzz checks","contributing.39fdec1194":"Tests","contributing.2d43f2b719":"Docker / Podman supported","contributing.e6443af99d":"Container","contributing.aafa53950c":"Rust toolchain, formatting, and lint checks","contributing.1493f62286":"Toolchain","contributing.6ed8d2034b":"Rust version per project","contributing.89b86ab0e6":"Language","contributing.a8aed5830a":"TECH SPECS","contributing.5442e2b64f":"HEDL on GitHub","contributing.technicalGuide":"Read HEDL's contribution guide","contributing.d47f7c3dec":"Dweve maintains fourteen technical foundations spanning maths, parsing, retrieval, policy, simulation and runtime verification. HEDL is public on GitHub; the rest publish in fortnightly rounds from 1 September 2026, two at a time to begin with. Start with each project licence and stated route before sending work.","contributing.5fb521eb4b":"sovereign AI systems.","contributing.1a35248d88":"Contribute to","contributing.661d868d65":"Foundations, Contributing","contributing.f9743247fa":"Read the documentation","contributing.e05b097379":"Browse HEDL on GitHub","contributing.8fb0a86410":"Browse the foundation pages. HEDL is public now, AION and Knot publish on 1 September 2026, and every other page names the round it is in. The project route explains how to ask for help.","contributing.87dfafc6f8":"Build sovereign AI with us.","contributing.a03e87437d":"Accepted contributions may be credited in release notes or a contributor record when the project keeps one. Check the project terms for any recognition or other benefit.","contributing.cb48949de0":"Recognition in the project record.","contributing.a08a2992e4":"RECOGNITION","contributing.6e563091f6":"Contributor sessions may be announced when a project schedules them. Check the project page or contact Dweve for current participation options; location, timing and support depend on the event.","contributing.2b090b237d":"Sessions when scheduled.","contributing.c5f548a22c":"SESSIONS","contributing.475c6c853b":"You can ask for contribution guidance through the project or contact route. Whether a maintainer can review a first change, which language is available and how quickly someone responds depend on the project and current capacity.","contributing.b08089799e":"One-on-one guidance.","contributing.76ee7438dc":"GUIDANCE","contributing.eadaea56d3":"Project guidance, community sessions and contribution records depend on the route you choose.","contributing.5e5ce1702e":"Guidance, sessions and project records.","contributing.3cef388a15":"What we provide","contributing.81b73fb093":"Contribution can feel intimidating. Start with a concrete question, report, documentation change or test. Where a repository exposes issue templates or an entry point, use it; otherwise request the current route through Dweve. Support and response time depend on the project.","contributing.faeb178497":"Support follows the project route.","contributing.5e829c70c2":"Support for contributors","contributing.e1ca6c1070":"Review practices depend on the project. Read its contribution terms to see who can review a change, which checks apply, how security concerns are handled and whether the discussion is public.","contributing.88de658988":"Maintainer review where required.","contributing.7066ae302d":"Check the licence and source-access terms for each project before integrating or sending work. If they are not stated, contact Dweve before use.","contributing.5e77f2e0e0":"Per-project licence and access terms.","contributing.0398ccd0f4":"LICENSE","contributing.fec3ac17f9":"Contribution terms vary by project. Check the repository or contact route for the applicable licence, review conditions and any agreement requested before submission.","contributing.4feaf02593":"Contribution terms.","contributing.7f564b82b0":"TERMS","contributing.48c805f9c0":"Contribution terms, licence and review vary by project.","contributing.9a3c3a53c5":"Contribution terms, licence and review.","contributing.524a4a815a":"How decisions are made","contributing.7b152e1dd7":"Contribution needs clear terms. Dweve describes the current access, licence and review route for each project. Repositories publish in fortnightly rounds from 1 September 2026, so check the project record before you commit time or submit work.","contributing.9af9a1cb7b":"Clear terms. Documented route. Shared responsibility.","contributing.823619e079":"Governance","contributing.129d7f278f":"Interface design, accessibility audits, iconography and brand assets. Designers can propose work for Fabric, the documentation site and project surfaces. Follow the available brand and accessibility guidance, and ask before reusing files or tokens.","contributing.192454f614":"User experience and visual design.","contributing.9b33bf4b96":"TRACK DESIGN","contributing.24f25d52f9":"Manual testing, automated test expansion, fuzz testing, and benchmarking. Testers verify that new releases work on real hardware and in real workflows. Fuzz testers find edge cases that deterministic logic should handle. Benchmarkers validate performance claims. This track is ideal for methodical thinkers who enjoy breaking things.","contributing.0afea427a9":"Quality assurance and verification.","contributing.4168a6c8ca":"TRACK TESTING","contributing.09ff09d67f":"API references, user guides, tutorials and translation. Technical writers can propose improvements through the documented project route, and most documentation tasks do not require coding. Check the project for its tooling and review process.","contributing.78ec8bca42":"Documentation and technical writing.","contributing.e62ce8b4d8":"TRACK DOCS","contributing.f828f6f11e":"Bug fixes, performance improvements, new features and refactoring. Several foundations use Rust, with other languages appearing where the project needs them. Follow the project's source-access, review and test instructions; public entry points are not guaranteed.","contributing.007e976e22":"Software engineering.","contributing.f6dd10560b":"TRACK CODE","contributing.e77dfbc28d":"Software engineering, documentation, quality assurance and design. The available project route and point of contact vary by foundation.","contributing.f4ac2f32b7":"Four tracks. Clear entry points.","contributing.c185ae4d3c":"Contribution tracks","contributing.bfab5c9f8c":"We organise contribution into four broad tracks. Each foundation describes its available route, scope and review terms. You can approach the work as an individual, university research group or engineering team, subject to the project access boundary.","contributing.2bcdd3312a":"Code, docs, testing, and design. Every skill has a place here.","contributing.9cac0f4335":"Ways to contribute","contributing.0cc056ee44":"Teams that contribute through a project’s route can build deeper expertise than teams that only consume it. Engineers learn the internals of systems they depend on and can develop relationships with maintainers when the project supports that contact.","contributing.6f91f74246":"Talent and expertise.","contributing.fcbfa876c2":"TALENT","contributing.496588812c":"A well-scoped contribution can inform a project's roadmap when its maintainers accept it. Organisations should treat contribution time as work with a clear scope, review route and access boundary, not as a promise of product control.","contributing.1ec899261c":"Strategic influence.","contributing.3285633c2f":"INFLUENCE","contributing.b2e19a0921":"Project visibility follows the release schedule. HEDL is public; every other foundation carries a public description now and its repository and documentation when its round arrives. Read each project documentation and licence before deciding what you can inspect, verify or reuse.","contributing.a868091e5f":"Transparent by design.","contributing.ae4214b7d0":"TRANSPARENCY","contributing.6f0243ae0c":"Dweve is incorporated in the Netherlands and develops in the European Union. Project licences, governance and data handling are described per project and may differ. Contributing does not by itself establish regulatory compliance; check the terms and evidence that apply to your use.","contributing.8cc66de3f1":"Jurisdiction and control.","contributing.eb8d72238c":"JURISDICTION","contributing.5cbdcb40c2":"Contributing gives you a way to examine how a project handles data, decisions and governance. Check the route and evidence that apply.","contributing.a74d3aeb23":"Jurisdiction, transparency, influence, and talent.","contributing.0a3488144f":"Why Dweve contribution matters","contributing.ce285678e2":"For organisations, contribution can be strategic when the project accepts the work. A well-scoped code, documentation or testing proposal can inform a roadmap while your team builds expertise in the technology it uses. Treat that influence as a project outcome, not as a promise of control or compliance.","contributing.6af876eea3":"Europe needs AI infrastructure whose ownership and operating boundaries can be examined. Dweve is building that alternative, but the contribution route is not identical for every foundation: HEDL is public and other source access is by request. Project pages and the contact route keep the current scope, review and access terms visible.","contributing.bc740771f2":"European AI sovereignty needs more than good intentions.","contributing.f32a339ea3":"Why contribute to Dweve","contributing.c8a233a8ee":"Project record","contributing.ee7b42aa6f":"Recognition","contributing.469ccb93de":"Sessions when scheduled","contributing.c5497bca58":"Community sessions","contributing.f62a13070e":"Subject to availability","contributing.da30b47c9b":"Guidance","contributing.04a6a4343c":"Europe-wide","contributing.bfd58ee3a2":"Community","contributing.3f65f2f602":"14 technical foundations","contributing.53e890d5f0":"Projects","contributing.79073eaaf2":"The Netherlands","contributing.44ab85a252":"Origin","contributing.bedc343248":"Stated per repository","contributing.3229609e15":"License","contributing.378eb0be27":"CONTRIBUTING","contributing.2aaafe5e77":"Dweve brings together engineers, writers, designers, testers and other people who care about sovereign, transparent and accountable AI. Some work is public and some foundations require source access by request. Whether you write code, document features, translate interfaces or test edge cases, the project route explains where your contribution can fit.","contributing.dc0daedcbc":"Europe’s AI infrastructure.","contributing.193d0d8595":"Help improve","contributing.3af21f392c":"Open the HEDL repository","contributing.bf52b2b6db":"Choose a project and check where it sits in the schedule. You can report a problem, suggest documentation, translate, or ask about a project that has not published yet.","contributing.7ff9bdde02":"Every contribution counts.","contributing.d83f167a00":"Start today","contributing.c78f6803ed":"A bug report does not have to be a stack trace. Something like: I tried to do X, I expected Y, the system did Z, and here is the screenshot. That is enough, and an engineer will translate it into something they can fix.","contributing.405d6d72ae":"Tell us a story","contributing.7d49e47eff":"When a project offers a beta, users who are not engineers can try the feature, describe what happened and note what was confusing. Real workflows can reveal rough edges.","contributing.be9ada4a15":"Test new features","contributing.deb990a4fc":"Our team writes in English, not in every language Dweve should reach. Native speakers can ask through the project or contact route about translation work, review and credit.","contributing.2be17aa181":"Translate","contributing.b314b7d383":"When a project publishes a new documentation page, fresh eyes help. Read the draft, mark confusing spots and suggest clearer wording. You can improve documentation without writing code.","contributing.73604199bf":"Read documentation drafts","contributing.1358e7723c":"Contributing, Consumer","contributing.b883472a8d":"Real impact","contributing.6cc2d9c85c":"Open to non-engineers","contributing.1d2ca67481":"Answer questions through the project or contact route.","contributing.a98aa4337e":"Community help","contributing.aa80fd9720":"A short writeup of what you wish existed.","contributing.4ba1bf0b84":"Feature ideas","contributing.75f50f7d4d":"Real-world stories beat synthetic test cases.","contributing.0b36698c5f":"Bug reports","contributing.8783c4ef49":"Try beta features, write what you experienced.","contributing.61c2b86f91":"User testing","contributing.606a0f9ee4":"Native speakers wanted for FR, DE, ES, IT, NL, PT, PL.","contributing.ac26a7a94e":"Translation","contributing.744b237f3b":"Read drafts, flag confusing parts, suggest clearer wording.","contributing.1c560c87b9":"Pick what fits","contributing.87bb73ee52":"WAYS IN","contributing.b15ee3c4e6":"STORIES","contributing.08e80e8771":"TRANSLATIONS","contributing.e670640574":"DOCS","contributing.67c0c12836":"is code","contributing.7df18eb746":"Not every contribution","contributing.b4445b651c":"Real ways to help","contributing.c686a26440":"No-code routes where documented","contributing.1f72791e55":"Documented no-code paths","contributing.054fc60c0f":"Dweve's contributor community includes engineers, writers, designers and advocates for privacy, transparency and digital sovereignty. Contact and discussion routes depend on the project; some are public and others begin with a source-access request.","contributing.a4b181f9a8":"Meet people who think like you.","contributing.ec32f63c50":"COMMUNITY","contributing.8e3139a0a0":"You can learn how software is built, tested and released by working through a project’s documented route. Feedback, tooling and the time required depend on the project and the contribution you choose.","contributing.60cbff8d7a":"Build real skills.","contributing.b9e4ab9527":"LEARNING","contributing.cfe41e6829":"Accepted contributions may be credited in release notes or a contributor list when the project maintains one. Check the project terms before assuming that a name, change or discussion will be published.","contributing.e47a80f1dd":"Your name in the project.","contributing.3ae9bc092d":"RECOGNITION","contributing.fd3311900a":"An accepted contribution can leave a lasting project record. The skills you build are real, while publication and access depend on the project terms.","contributing.c57ab439fa":"Recognition, learning, and community.","contributing.7a8cfa0e8c":"What contributors receive","contributing.f7fcbfc063":"When you help improve a project like Dweve, you can build skills and connect with people who care about the result. Recognition, publication and other benefits depend on the project terms.","contributing.d38e3281a6":"Contributing is not just generous. It is good for you too.","contributing.0a786b5121":"What you get back","contributing.827d3fd47d":"We believe that sovereignty starts with accessibility. That means Dweve should speak your language, not just English. If you are fluent in Dutch, German, French, Spanish, Italian, Portuguese, Polish, or any other language, you can help translate interfaces, documentation, and error messages. A well-translated product feels native, builds trust, and reaches people who would otherwise be excluded.","contributing.f751394b38":"Bring Dweve to your language.","contributing.5b4afb1ec1":"If you read a guide and had to re-read a sentence three times, that sentence needs work. If a tutorial skips a step that left you stuck, that step needs to be added. Documentation contributions can be as small as fixing a typo or as large as rewriting an entire guide. Every improvement helps the next person who comes along. Good documentation is written by the people who actually use it.","contributing.a88b964c15":"Make things easier to understand.","contributing.d2f2877dfc":"When something does not work as expected, use the project's issue or contact route and describe what you did, what you expected and what actually happened. Include evidence such as logs or screenshots when the route allows it. You do not need to know why it broke; describe what you saw.","contributing.e49ede180b":"Tell us what broke.","contributing.664f572fef":"BUG REPORTS","contributing.5f0c6cd090":"Whether you spot bugs, write clearly or speak multiple languages, a documented contribution route may fit.","contributing.9ed1c0643e":"Here","contributing.7cc06a4a2e":"Contribution is not only for programmers. People who spot problems, explain things clearly or speak another language can improve a project. If a button label is confusing, a feature breaks or a guide is missing in your language, describe the point where you got stuck and use the documented route.","contributing.041375ea29":"Three ways to make a real difference without writing code.","contributing.2ad437b6cc":"How anyone can help","contributing.8eb355f726":"Dweve, The Netherlands","contributing.eae192773b":"Made by","contributing.30937d0e29":"Time depends on scope","contributing.6c82e6dd86":"Time","contributing.75f527181b":"Terms vary","contributing.64ae43e8fe":"Cost","contributing.482b2a8555":"Recognition, learning, community","contributing.8ac7aa173f":"What you get","contributing.895eea6571":"Bug reports, docs, translations","contributing.9627fb89ef":"Ways to help","contributing.fedb4e3f40":"People with relevant skills","contributing.60d16ac941":"Who can help","contributing.38c963e7f6":"A guide to helping Dweve improve","contributing.f8c94a3b4b":"What it is","contributing.4e6a22430e":"AT A GLANCE","contributing.efb6c1c15d":"You do not need to be a programmer to help improve technology. Start with an issue, documentation fix, translation, test or review where the project provides that route; otherwise contact Dweve for source access or guidance. A clear report or explanation in your own language can make the next change easier to understand.","contributing.75665816e8":"the tools you use.","contributing.d7d8bd4a99":"Your voice shapes","contributing.a184a24106":"WAYS IN","contributing.b0cf9c1288":"no-code route where documented","contributing.33b68f3d34":"WHAT YOU GET","contributing.48fb71763d":"lasting","contributing.03ef6c29c3":"DOCS","contributing.0d5d4ebd6f":"LANG","contributing.94ee059335":"TEST","contributing.6e41ac8dae":"BUGS","contributing.41a677f9f3":"IDEAS","contributing.7928371f73":"COMMUNITY","contributing.75ae442cf2":"PATH 01","contributing.2e6f781582":"PATH 02","contributing.f96f235391":"PATH 03","contributing.d2747ee364":"PATH 04","contributing.850be92fa1":"strategic","contributing.2dcf75e599":"FOUR TRACKS","contributing.b981dc0e6d":"project-specific route","contributing.c9766ca413":"GOVERNANCE","contributing.05598e9ce1":"documented","contributing.f86a4f7635":"PILLAR","contributing.ce929eca09":"WHAT WE PROVIDE","contributing.7abe8cd76a":"for you","contributing.cedfc3f443":"THREE SETUPS","contributing.961d07d27d":"reproducible path where documented","contributing.41ff0cab75":"QUALITY GATES","contributing.d7e203bd43":"each change where required","contributing.dd3bfe5f7d":"GATE","contributing.b993e169e1":"FORK TO MERGE","contributing.84d6ee3592":"documented steps","contributing.6e10953f3e":"ROUTE","contributing.a0d4a6737a":"YOU","contributing.79ffa1c22b":"EUROPE","contributing.6ee9657aa8":"ENTRY","contributing.fda8c6bc13":"RULES","contributing.a42b8352b4":"SUPPORT","contributing.416861c7e2":"ENV","contributing.d8aefe6148":"GATES","contributing.59c05f1edb":"FLOW","contributing.fb745bfb95":"Make a real difference","contributing.6ac4e657ac":"Without code","contributing.1ffcd24889":"Contribution gives back","contributing.76e4987c88":"To you too","contributing.311ae71748":"Sovereignty needs","contributing.964923167b":"more than intent","contributing.c6d067bc44":"Every skill matters","contributing.ab95cc9475":"Clear rules","contributing.8ad8204c97":"Fair process","contributing.2a1823d0eb":"Support the people","contributing.350671420b":"who do the work","contributing.8d16a23235":"Rust and containers","contributing.334fcbda54":"Ready where documented","contributing.ccebfec3b9":"Checks carry the proof","contributing.ad8eeb420f":"Before merge","contributing.d8d9950e1f":"Fork to merge","contributing.pill.noCodeNeeded":"NO-CODE ROUTE","contributing.pill.realSkills":"REAL SKILLS","contributing.pill.code":"CODE","contributing.pill.design":"DESIGN","contributing.pill.publicReview":"DOCUMENTED REVIEW","contributing.pill.tests":"TESTS","contributing.pill.ciEnforced":"DOCUMENTED CHECKS","contributing.foot.pickOne":"pick one","contributing.foot.weHelp":"we help","contributing.foot.beyondCv":"beyond a CV","contributing.foot.forYears":"as recorded","contributing.foot.notJustConsuming":"not just consuming","contributing.foot.investing":"investing","contributing.foot.leadMaintainer":"a project contact","contributing.foot.valuedEqually":"scope explained","contributing.foot.protectsContributors":"keeps terms visible","contributing.foot.sustainsProject":"keeps scope clear","contributing.foot.removeBarriers":"we clarify the route","contributing.foot.lastingRelationships":"project context","contributing.foot.localTenMinutes":"local setup where documented","contributing.foot.ciMatched":"checks where documented","contributing.foot.noExceptions":"documented gates","contributing.foot.evenFounders":"same stated rules","contributing.foot.signedCommits":"project conventions","contributing.foot.ciGated":"checks where required","contributing.visual.waysAvailable":"ways available","contributing.visual.whatYouReceive":"what you receive","contributing.visual.startWhereYouFit":"start where you fit","contributing.visual.tracksOneBacklog":"tracks, project-specific access","contributing.visual.leadMaintainerBacklog":"project contact, current route","contributing.visual.noExceptions":"documented gates","contributing.visual.required":"where required","contributing.visual.stepsForkToMerge":"steps, access to review","contributing.visual.open":"route","contributing.visual.consumerWaysTitle":"Choose your way in","contributing.secondary.consumerWays.kicker":"What makes a report useful","contributing.secondary.consumerWays.leftLead":"Notice the moment","contributing.secondary.consumerWays.left":"Start with the moment you noticed. A confusing label, a missing instruction, or a feature that behaved unexpectedly is enough to matter.","contributing.secondary.consumerWays.rightLead":"Leave a clear trail","contributing.secondary.consumerWays.right":"Describe what you tried, what you expected, and what you saw. That gives a maintainer a concrete place to begin, even when you do not know the technical cause.","contributing.secondary.consumerReturn.kicker":"A record you can keep","contributing.secondary.consumerReturn.leftLead":"Make the work visible","contributing.secondary.consumerReturn.left":"Recognition makes the work visible. A corrected guide, translation, or report can help people you will never meet.","contributing.secondary.consumerReturn.rightLead":"Build practical skill","contributing.secondary.consumerReturn.right":"The practical value comes from doing the work through a documented route. You can practise how software is explained, tested and improved with feedback from people who care about the result.","contributing.secondary.businessInfluence.kicker":"Influence through the shared work","contributing.secondary.businessInfluence.leftLead":"Carry responsibility","contributing.secondary.businessInfluence.rightLead":"Keep review visible","contributing.secondary.businessInfluence.right":"Contribution is not a separate priority channel. It is work with a project scope and review route, so an organisation gains influence by carrying real responsibility where the project accepts it.","contributing.secondary.businessTracks.kicker":"Choose the work, keep the scope clear","contributing.secondary.businessTracks.leftLead":"Name the kind of work","contributing.secondary.businessTracks.left":"Code, documentation, testing, and design need different forms of judgement. The track tells a newcomer which kind is needed before anyone asks them to navigate the whole programme.","contributing.secondary.businessTracks.rightLead":"Respect the project route","contributing.secondary.businessTracks.right":"A shared review standard does not make the work identical. Each project explains whether a proposed improvement can be assessed publicly or must begin with a source-access request.","contributing.secondary.technicalEnvironment.kicker":"Two ways to prepare the same change","contributing.secondary.technicalEnvironment.leftLead":"Prepare locally","contributing.secondary.technicalEnvironment.left":"The local path stays deliberately small where source is available: prepare the documented toolchain, build the project, run the applicable tests, then use the stated review route.","contributing.secondary.technicalEnvironment.rightLead":"Use the documented container","contributing.secondary.technicalEnvironment.right":"Where a project provides a container route, it can place the documented toolchain and debugging tools in one reproducible environment. Check its supported targets and CI record.","contributing.secondary.technicalGates.kicker":"The change has to carry its evidence","contributing.secondary.technicalGates.leftLead":"Match checks to risk","contributing.secondary.technicalGates.left":"Tests, measurements, and documentation cover different failure modes. Together they let a reviewer assess the proposed change rather than rely on its author.","contributing.secondary.technicalGates.rightLead":"Leave reviewable evidence","contributing.secondary.technicalGates.right":"The gate is deliberately ordinary: make the change legible, run the checks that apply, and leave a record someone else can review.","contributing.secondary.consumerPaths.kicker":"A path you can recognise","contributing.secondary.consumerPaths.leftLead":"Start with evidence","contributing.secondary.consumerPaths.left":"A useful contribution begins with a real point of contact. If you can explain where a reader, user, or teammate gets stuck, you already have a starting point.","contributing.secondary.consumerPaths.rightLead":"Choose a good fit","contributing.secondary.consumerPaths.right":"Choose a task that suits the way you notice problems. A small correction with a clear reason is easier to review than a grand plan without evidence.","contributing.secondary.businessGovernance.kicker":"Clear terms, practical decisions","contributing.secondary.businessGovernance.leftLead":"Know the terms","contributing.secondary.businessGovernance.left":"Clear project terms give contributors a way to raise concerns and see how a decision is made. They keep responsibility attached to the work.","contributing.secondary.businessGovernance.rightLead":"Test the boundary","contributing.secondary.businessGovernance.right":"For an organisation, the current project terms matter as much as the policy. They show what can be proposed, who can review it and which access route applies.","contributing.secondary.businessSupport.kicker":"Support that leaves the work stronger","contributing.secondary.businessSupport.leftLead":"Remove a constraint","contributing.secondary.businessSupport.left":"Useful support removes a real constraint: time for review, access to a domain expert, or a test environment that lets a change be checked properly.","contributing.secondary.businessSupport.rightLead":"Strengthen the process","contributing.secondary.businessSupport.right":"The aim is not a special lane for one contributor. It is a stronger shared process that the next team can use too.","contributing.secondary.technicalWorkflow.kicker":"Small steps, shared history","contributing.secondary.technicalWorkflow.leftLead":"Make a small change","contributing.secondary.technicalWorkflow.left":"The workflow does not ask for a perfect first patch. It asks for a change with a clear purpose, a reviewable branch, and checks that match its risk.","contributing.secondary.technicalWorkflow.rightLead":"Keep shared history","contributing.secondary.technicalWorkflow.right":"Review can turn the work into shared history. Where the project records commits, discussion and test results, those artefacts show what changed and give the next maintainer a place to begin.","contributing.banner.consumer.headline":"Every contribution","contributing.banner.consumer.headlineAccent":"counts.","contributing.banner.consumer.bodySecond":"A clear report, translation, or correction gives the next contributor a concrete place to begin.","contributing.banner.consumer.instrument":"Choose your entry point","contributing.banner.consumer.tag":"OPEN","contributing.banner.consumer.verdictLabel":"A useful start","contributing.banner.consumer.verdictValue":"One concrete report is enough.","contributing.banner.consumer.footer":"Contribution, clearly recorded.","contributing.banner.business.eyebrow":"Contribute in the open","contributing.banner.business.title":"Bring a question","contributing.banner.business.headlineAccent":"to the project route.","contributing.banner.business.body":"Start with work that needs doing and a scope the project can review. A documented process gives an organisation a durable way to help.","contributing.banner.business.bodySecond":"Influence comes from carrying a real responsibility through the review route the project documents.","contributing.banner.business.instrument":"Contribution routes","contributing.banner.business.tag":"OPEN","contributing.banner.business.verdictLabel":"Shared process","contributing.banner.business.verdictValue":"The work can be reviewed.","contributing.banner.business.footer":"Project terms, documented review.","contributing.banner.businessClose.headline":"Build the base","contributing.banner.businessClose.headlineAccent":"with others.","contributing.banner.businessClose.bodySecond":"The strongest support leaves a more capable process behind for the next contributor and the next team.","contributing.banner.businessClose.instrument":"Support made visible","contributing.banner.businessClose.tag":"OPEN","contributing.banner.businessClose.verdictLabel":"A durable contribution","contributing.banner.businessClose.verdictValue":"The shared work is stronger.","contributing.banner.businessClose.footer":"Support, review and a project record where available.","contributing.banner.technical.headline":"Make the change","contributing.banner.technical.headlineAccent":"reviewable.","contributing.banner.technical.bodySecond":"A small patch with evidence is more valuable than a large change that no one can safely inspect.","contributing.banner.technical.instrument":"Review path","contributing.banner.technical.tag":"CHECKED","contributing.banner.technical.verdictLabel":"Ready for review","contributing.banner.technical.verdictValue":"Tests and intent travel together.","contributing.banner.technical.footer":"Change, evidence, review.","contributing.footer.consumer":"Contributing, Consumer","contributing.footer.business":"Contributing, Business","contributing.footer.technical":"Contributing, Engineer","contributing.consumer.paths.body":"A lot of people read the word ‘contribute’ and assume ‘code’. Many useful contributions are not code. Documentation reads better when a non-engineer reads it first. Translations need native speakers. Designs need people testing them. Bug reports need real-world stories, not synthetic test cases. Choose a route that matches what you naturally do well, subject to the project's access terms. The routes shown below are the ones that are documented today. Start from something you actually noticed rather than from a task list.","contributing.b1288b5d32":"Document the step that applies","contributing.dc167ffb2b":"Start where you are","contributing.7c98d3557e":"You do not need to write code","contributing.151016c9b4":"to make the project better","contributing.b2316c55ba":"A bug report with a reproduction, a page of documentation that finally reads clearly, or a translation that a native speaker trusts all change the project. Pick one, open it in the open, and someone here will meet you there.","contributing.ac40e1aefa":"How to help","contributing.e570d7109a":"OPEN TO EVERYONE","contributing.0499685e7e":"Every contribution is reviewed in the open","core-extras.96d330537a":"Base IR","core-extras.bee831a169":"Substrate","core-extras.61a0822826":"Apps on Core","core-extras.15438cc098":"not supported","core-extras.ad565d9d01":"Feature","core-extras.0155bf03e5":"Segment legend","core-extras.8b7110078e":"Algorithm groups by data type","core-extras.25ab4276a6":"Scrollable capability matrix","ctb-hero-glyph.490c178c15":"squash and credit","ctb-hero-glyph.1e0d71f7c2":"MERGE","ctb-hero-glyph.b75cb3a046":"1 approval","ctb-hero-glyph.ed6912ad70":"REVIEW","ctb-hero-glyph.b477751d76":"FORK","ctb-hero-glyph.12b2b7105f":"MAIN","ctb-hero-glyph.mainSub":"documented project route","page-breadcrumb.c766e66518":"Breadcrumb"}