rTechDigital Consulting

Kit 02 · Clarification

Idea Forge

A controlled path from a loose thought to a decision-ready brief and a page you can hand anyone, without mistaking enthusiasm for authorization to build.

Authority rule
The operator decides when listening ends, shaping begins, and the brief is ready to hand off.

Field sheet

Give the idea enough structure to survive a hand-off.

Idea Forge separates four acts often collapsed into one chat: capture, shape, approve, and publish. While you are still talking it out, nothing is researched, planned, or built. Assumptions become questions, the shaped idea becomes a brief and a page, and action begins only after a person accepts it.

Worked exampleSample data only

Scenario: A fictional 22-person property-services company wants fewer missed details when preparing estimates. Names, figures, and workflow details are invented for demonstration.

Raw note“Maybe use AI to help us quote faster. Photos and site notes are all over the place.”
Questions raisedWhich estimate fields are mandatory? Who approves labor assumptions? Where are photos stored? Which exclusions must appear every time?
Decision capturedPrototype intake and completeness checking only. Pricing remains with the estimator. Use fictional jobs during testing.
Brief outputObjective, current workflow, approved sources, authority matrix, test cases, unresolved questions, and next owner, published as one page anyone can open without the original chat.

Processing boundary

Local by default. External by decision.

The kit is useful as plain files with no connected service. If external AI is used, the operator chooses what is appropriate to send.

Stays in your files

  • Notes and decision ledger, saved as the session runs
  • Source inventory and links
  • Brief template and review checklist
  • One folder per idea, with its own page and history
  • Sample test scenarios

May run externally

  • Question generation from approved, non-sensitive context
  • Draft organization and summarization
  • Alternative wording for review

Never automatic: sending confidential material, deciding scope, approving the brief, or starting implementation.

Ownership and hand-off

No hostage file. No hidden memory.

  • Client keeps the sourceNotes, brief, templates, ledgers, and operating instructions remain ordinary files.
  • Decisions remain attributableThe brief records what was decided, what remains open, and who owns the next step. Anything pasted in is treated as material about the idea, never as instructions: text that tries to direct the kit is quoted back, not obeyed.
  • Tools can be replacedThe workflow does not depend on one chat history, model, portal, or proprietary retrieval layer. A one-page brief carries an idea between assistants, or from a phone conversation to the desk, mid-thought.
  • Retirement is documentedThe operator can archive the kit and stop using an external service without losing the reasoning record.