Local AI
Choose between Ollama, LM Studio and Open WebUI. Build a first local setup, test the output and understand the limits.
Open the practical tool guide →THE WORKSHOP / CONNECTIONS 001
Built together.
Earned through craft.
Useful software, intelligent systems and imaginative worlds. The Network connects the work coming out of Rookweld with people who can help it grow.
OPEN INVITATION · NO PARTNER AGREEMENTS ANNOUNCED01 / THE RESOURCE BENCH
Tools worth your time.
Judgment before endorsement.
Start with the problem and evidence. These independent workshop notes explain an approach; product links retain their current release or experimental status.
Development
Builds, version control and deployment evidence. Make a release reproducible before making it public.
Read the release note →IT Toolkit
Diagnostics and practical technician workflows. Inspect first; preserve a way back before changing a system.
Read the diagnostics note →Game Creation
Characters, quests and worlds with room for human authorship. Explore deterministic generation in CharacterForge.
Explore the experimental preview →FROM THE WORKSHOP / NEW BUILD DIARY
A local assistant.
With a bird of its own.
Mini-Rook is taking shape: Python, Ollama, three conversation modes and a curated notebook. Follow the recorded tests, the next questions and the current setup notes.
Experimental prototype · No public Mini-Rook package yet · No comparative benchmark claimed.
02 / FOUNDING PARTNERS
Help build
what comes next.
Rookweld is an independent, product-led technology studio in Sweden. We welcome early collaborators who can help turn useful prototypes into sustainable products. This is an invitation to discuss a fit, not a list of secured sponsors.
Tools & infrastructure
Development credits, software licenses, API access, test environments and loaned evaluation hardware that solve a specific product need.
SUPPORT SOUGHT · SCOPE AGREED INDIVIDUALLYIntegrations & validation
Early-access tools, technical expertise and focused integration work with an agreed scope and inspectable results.
SUPPORT SOUGHT · SCOPE AGREED INDIVIDUALLYReach & introductions
Relevant creator and developer communities, thoughtful introductions and shared demonstrations of useful software.
SUPPORT SOUGHT · SCOPE AGREED INDIVIDUALLYWhat the workshop can offer
A focused integration, honest technical feedback, a practical implementation write-up or a joint demonstration. Scope, evidence, usage rights and any public placement are agreed in writing. Support never buys a positive review or a ranking.
Explore sponsorship offers ↓PARTNER HUB / SCOPED SPONSORSHIP
Sponsor useful work.
Rookweld is an early-stage independent workshop. These offers fund technical work and useful content. We do not promise audience size, traffic, sales or a positive review. Every enquiry is assessed for fit and available capacity.
Technical field test
Developer tools, local AI software and technician utilities.
Deliverable: One agreed workflow evaluated, with recorded setup, observations, limitations and a clearly labelled technical article.
Example: Can this tool help an IT technician summarise a fictional ticket without inventing facts?
Support: A scoped project fee; evaluation access or a loaned device may be agreed separately.
INDIVIDUAL QUOTE · SCOPE AGREED BEFORE WORKRequest this collaboration →Integration field note
APIs, SDKs, hosting and software that fits the Rookweld workshop.
Deliverable: One bounded example integration plus a practical article covering setup, implementation and known limits. Shareable sample code is agreed in scope.
Example: Connect a developer API to a small Python workflow and document the result.
Support: A scoped project fee, with any API access, credits or licenses specified separately.
INDIVIDUAL QUOTE · SCOPE AGREED BEFORE WORKRequest this collaboration →Workshop development support
Partners who want to support a defined Rookweld product milestone.
Deliverable: An agreed milestone report describing the work, outcome and limitations, with a disclosed supporter acknowledgement when public placement is agreed.
Example: Support a specific compatibility test or development task for an existing Rookweld tool.
Support: Funding, relevant development credits, licenses or loaned equipment against a defined need.
INDIVIDUAL QUOTE · SCOPE AGREED BEFORE WORKRequest this collaboration →A clear agreement before the first task.
- Agree the deliverable, fee or in-kind support, timing, acceptance criteria and usage rights in writing. This page does not accept an order or start a project.
- Fees cover the agreed work. Credits, licenses and loaned hardware are recorded separately; they are not reported as earned cash revenue.
- Paid work and supplied resources are disclosed alongside the relevant article or acknowledgement. A sponsor may flag factual errors; editorial findings remain independent.
- Content reuse, advertising rights and exclusivity require a separate agreement. Public sponsor placement does not imply endorsement or certification.
Send the product, a useful test or integration idea, the support or budget available and the desired timing. We will discuss scope before quoting.
03 / FROM THE FORGE
Our work
comes first.
CharacterForge
Procedural characters, quests and creative building blocks. Explore the current preview, its limitations and release verification.
Open CharacterForge →RealityOS
Local intelligence, agents and coordinated workflows. Explore The Map as an illustrative web demo, with its boundary clearly stated.
Explore The Map →ForgeCare
Windows technician tools and an inspectable engineering story. See the product page for current release details.
Open ForgeCare →04 / ORIGINAL FIELD NOTES
Practical starting points.
Editorial guidance · published 9 October 2026 · not a benchmark, vendor certification or product endorsement.
Start with one repeatable workload.
Choose a small task you can judge: summarising a non-sensitive document, classifying a test ticket or drafting code against a known example. Keep the input and expected outcome so you can compare models on the same task.
- Record the model, runtime, hardware and settings. Measure response time and inspect the output.
- Begin with read-only tools and disposable data. A plausible answer is not permission to change files or systems.
- Check memory and temperature during sustained use. Reduce the workload when your machine cannot run it reliably.
- Add routing, memory and automation only when the basic task works consistently.
Read the full local AI tool guide →
A useful outcome is a reproducible result with known limits. RealityOS explores the next layer →
A release needs a way back.
A successful build is one piece of release evidence. Keep the source revision, commands, artifact checksum and known limitations together so another person can understand exactly what they are testing.
- Build from a recorded revision and run checks against the resulting artifact.
- Test a clean installation or extraction with disposable data. Record the operating system and required dependencies.
- Keep the last working release and document how to restore it before replacing a live version.
- Label experimental features and unsigned packages clearly; publish verification alongside the download.
Check reproducibility before expanding the audience. See the CharacterForge release dossier →
Inspect before you change.
Write down the symptom, when it began and what changed recently. A useful diagnostic session narrows the cause while preserving the system's recoverability.
- Collect relevant version details, logs and resource measurements. Exclude credentials and personal data from shared evidence.
- Form one testable hypothesis. Change one variable and record what happened.
- Back up affected data and save a rollback path before cleanup, driver changes or service reconfiguration.
- Repeat the original failing workflow after the fix. Record unresolved symptoms instead of declaring success from a single healthy screen.
Prefer a small supported correction to an unexplained batch of changes. Read the ForgeCare case study →
05 / WORK WITH ROOKWELD
Bring a useful problem.
Or a useful connection.
Tell us what you want to build, what support you can offer and what a useful first outcome would be. Enquiries are reviewed by Pontus Lindh / Nullfeather; there is no guaranteed response time or automatic acceptance.
Email Pontus Lindh ↗06 / TRANSPARENCY
Trust is part of the work.
Independent recommendations
No paid placements, affiliate links or confirmed partner relationships are introduced on this page. A resource or product mention does not imply a commercial relationship.
Clear commercial labels
Future paid work, supplied equipment and affiliate links will be labelled beside the relevant content. Partners cannot purchase a positive evaluation. No partner logos are displayed without an agreed relationship and permission.
Privacy & enquiries
This page adds no tracking, cookies, signup form or visitor database. Email opens your own mail application. Share only information needed to discuss the work; do not send passwords or sensitive records. Ask through the same contact address about access to or deletion of enquiry correspondence.