Hidden Alchemy
An open engineering laboratory that turns raw ideas into real systems — in public, one human decision at a time.
open source
security-reviewed automation
honest lifecycle statuses
no vanity metrics
LIVE DASHBOARD · REGENERATED DAILY BY org-pulse
NEXT GATE · CONCEPT
The flagship idea-forge is mid-concept — its research is public, and the next human gate is Architecture. Every transition stays a decision, never an automation.
QUICK PATHS · ONE CLICK TO ACTION
➜ Submit an idea enter the pipeline |
➜ Membership interest a reviewed status |
➜ Propose a system a concrete idea |
➜ Idea board track the pipeline |
STAGE SYSTEM
Every repository occupies one stage of the same pipeline. Most good ideas die somewhere between concept and execution — this lab's whole job is closing that gap, in public, so the process can be inspected and shared.
01 · IDEA A raw idea is written down and submitted — nothing more. |
02 · CONCEPT CURRENT Examined for actual value and boundary — what it is, what it is not. |
03 · ARCHITECTURE The shape of the system is decided before any code exists. |
04 · SYSTEM A working thing exists: built, tested, honest about its limits. |
05 · AUTOMATION The repetitive parts are automated so the system creates leverage. |
06 · REALITY Used, maintained — and when its time passes, archived with a reason. |
IDEA ✓
CONCEPT ◉
ARCHITECTURE
SYSTEM
AUTOMATION
REALITY
Current lock: CONCEPT — the
idea-forge flagship. Every transition stays a human decision.DOMAIN TERRITORY
Where the process is currently applied — not everything software can be, the lab's actual territory.
F · FRAPPE & ERPNEXT ▸ Purpose-built systems on the Frappe Framework ▸ ERPNext customization, custom DocTypes ▸ Workflow engineering & integrations |
AI · AI & AUTOMATION ▸ AI that observes, reasons, executes ▸ Agentic workflows, orchestration, assistants ▸ Never an "AI button" for its own sake |
S · SOFTWARE & PRODUCT ▸ Architecture, usability, maintainability ▸ Developer experience, the discipline of shipping |
R · RESEARCH & EXPERIMENTATION ▸ Genuine investigation, small labeled experiments ▸ Failure is a recorded outcome — never a secret |
LIVE INVENTORY
Operational repositories and their lifecycle status. Only things that genuinely work are listed. Health verified 4/4 by the org-wide
repo-health-check.
active · running infra
concept · researched, not yet built
EXPERIMENT ZONE
Short-lived, honestly-labeled explorations that have not yet earned a dedicated repository: a hypothesis, an objective, a status, a next step — and, when appropriate, a recorded dead end.
Idea intake |
Experiment scratch Short-lived experimental code lives in an experiments repository — created only when the first real experiment exists, never before. Not every experiment becomes a product; that is intentional. |
FIRST CONTRIBUTION
Anyone can contribute publicly without any membership — here, or anywhere on the pathway below.
Your entry point is one of these, or a direct pull request to documentation:
Found a bug? Reproduce it, report it. |
Have an idea for the lab? Raw ideas are welcome at the top of the pipeline. |
Proposing a concrete system? Go straight into the pipeline. |
Documentation fix? Open a PR directly — no pre-approval for small fixes. |
Before your first contribution, read the Code of Conduct — it is short and worth the two minutes.
THE CONTRIBUTION LADDER
Every tier below is earned through observable, sustained contribution — role titles are deliberately professional, not gimmicky. The recognition log is the honest ledger.
THE COMPACT LIST
i Build, Don't Perform What works matters more than what looks impressive in a demo. |
ii Complexity Becomes Invisible Good engineering hides unnecessary complexity from the user. |
iii Automation Creates Leverage Automate what shouldn't require human repetition — not everything. |
iv Design Is Part of Engineering A technically correct system can still be a bad product. |
v Experiment Relentlessly Prototype. Break. Measure. Refine. Repeat — and record the outcome honestly. |
vi Details Compound Small decisions become large differences when repeated across a system. |
THE THRESHOLD
Membership is earned through contribution, not requested on demand.
Organization membership is a separate, reviewed status — it is not the same as contributing. Anyone can contribute publicly without ever becoming a member. The bar, plainly:
| 1 | Earn it first. Be a Recognized Contributor: at least three accepted contributions spanning at least a month. |
| 2 | Submit the Membership Interest form in the community repository. |
| 3 | Review, recorded. A human maintainer checks against published criteria; the decision is written on the issue. Invitations are always sent manually — never automated. |
Field notes — what people usually ask
How do I know what stage a project is in?
Every repository carries its current pipeline stage and a lifecycle status tag (ACTIVE, CONCEPT, EXPERIMENT, ARCHIVED) in its README — and the org-wide
repo-health-check verifies those stay honest. The live Org Pulse snapshot at the top of this page repaints the same story every day.What counts as a contribution?
A merged pull request, or an idea that is promoted into a real repository. At least three accepted contributions spanning at least a month earn the Recognized Contributor tier — the bar for the Membership Interest form.
Can I join as a member on day one?
No — membership is earned through contribution, not requested on demand. But it is never required either: you can contribute publicly without any membership at all, at every tier above the membership line.
Does automation ever approve anything?
Automation only assists — labelling, welcome messages, stale reminders. Decisions that change a project's stage or a person's membership are always made and recorded by a human.
ideas community idea board .github
This profile is intentionally honest about the current state of the lab — infrastructure first, projects as they become real.
raw ideas, forged publicly
