What does a TimeWaver analysis actually show?
An analysis produces a prioritized list of database entries — each one a short text the system has surfaced as resonant with your profile and focus text at this moment. Every entry carries the same anatomy: the database it came from, a relevance percentage, an intensity value, and (where applicable) a potency band.
The single most common mistake is reading the list like a lab report. It is closer to a mirror held up to an inquiry: the machine evaluates millions of entries against real-time quantum noise patterns and surfaces what resonates most with the question you encoded. The output's usefulness depends almost entirely on how well you read it.
What does the relevance percentage mean?
Relevance expresses how strongly an entry resonates with the profile and inquiry right now — it is not a score, a severity rating, or a pass–fail line. In group work we read it as "this theme is resonating at N% of the group." A high percentage says look here; it does not say something is wrong here.
In practice, entries clearing roughly the 62% line deserve attention first, and the question worth asking is never "do we fix it?" but "do we address it — or leverage it?" Some of the strongest readings we facilitate treat a 90%+ entry as an asset the organization has not yet claimed.
What are intensity, potency and exponents?
Alongside relevance, entries carry an intensity value and — for remedy-style databases — a potency band expressed in exponents. Think of these as depth markers: lower bands tend to speak to what is immediate and situational, higher bands to patterns that are older, more structural, more identity-level.
You do not need to memorize the numerology. You need a working rule: the higher the band, the slower and deeper the conversation it belongs in. A high-potency entry surfacing in a team scan is rarely about this week's project — it is usually pointing at a long-held pattern the team has learned to work around.
How do I turn an entry into meaning?
This is the heart of decoding, and the move that separates a confident reading from a confused one: read the machine's own words aloud, then turn the entry's vocabulary into open questions. Never invent a theme when the entry's text already supplies one.
- Quote it. Read the entry text exactly as written — no paraphrase yet.
- Locate it. Which database did it come from, and what does that discipline mean by these words?
- Weigh it. Relevance, intensity, potency — how loudly and how deep is it speaking?
- Question it. Convert its exact vocabulary into open questions — Where else…? How can…? What would…? — asked at two levels: the group in the room, and the organization as a whole.
Questions stay open (never yes/no), appreciative, present-tense, and one breath long. They address roles, never named individuals. And when an entry seems opaque — a Feng Shui symbol in a business scan, say — the discipline is research, never dismiss: look up what the entry means inside its own tradition, then map the metaphor onto your inquiry.
Your team runs scans but the outputs still feel arbitrary? That is the exact gap our four-session Foundations training closes — from raw list to confident, decoded, business-relevant reading.
Enquire About TrainingWhat does a full decoding protocol look like?
In training we teach decoding as a repeatable seven-step protocol, so any trained team member produces a reading another member can follow. The protocol moves from context to action:
Why do TimeWaver outputs feel confusing or arbitrary?
Almost always for one structural reason: the databases speak the languages of other disciplines. Most of TimeWaver's million-plus entries were authored by medical, homeopathic and psychological practitioners for their own fields. When an organization reads those entries without that grounding, the outputs feel random — and skepticism grows where confidence should.
The durable fix is twofold. First, train the decoding competency this guide sketches. Second — for organizations going deep — build a database in your own language, so the machine answers in vocabulary your team already owns. When the rubric is yours, the outputs make sense.
Common misreadings — and what to do instead
| Common misreading | What to do instead |
|---|---|
| Treating relevance % as a severity or pass–fail score | Read it as resonance: "look here first" — then ask whether to address or leverage |
| Paraphrasing entries from memory | Quote the entry's exact words; the vocabulary is the data |
| Dismissing opaque entries as noise | Research the entry inside its own tradition, then map the metaphor |
| Naming individuals in a group reading | Speak to roles and patterns only — never persons |
| Expecting identical results on re-scan | Each analysis reflects its moment; track themes across scans, not single entries |
| Reading every entry in the list | Group into themes; depth beats coverage |
Want the full protocol taught live, on your machines, with your real inquiries? Corporate Foundations training starts at SGD 15,000 for up to 10 participants — or take a seat in the open quarterly cohort.
See Programs & PricingThe TimeWaver Field Notes
Decoding insights, straight to your inbox
Occasional field notes from real trainings — decoding techniques, honest research notes, and first access to quarterly cohort seats and session openings.
By joining, you agree to receive the TimeWaver Field Notes by email. Unsubscribe anytime.
What this guide is not
This is not a medical interpretation manual, and TimeWaver results are not diagnoses. TimeWaver is used in this work as a consciousness and information-field support tool. It is not presented as a conventional diagnostic instrument or a replacement for medical, psychological, legal, or financial advice. The scientific mainstream does not recognize Information Field theory; we teach the tool inside that honest frame, as a complementary instrument for reflection and alignment.
Frequently asked questions
Why are my TimeWaver results different every time?
Because an information-field analysis reflects the moment it is run — the focus text, the practitioner's state, and the context all shape what surfaces. Repeatability in the laboratory sense is not the design; relevance to the inquiry at hand is. That is why a clean focus text and a clear practitioner matter more than repetition.
Is a high relevance percentage good or bad?
Neither. Relevance is not a pass–fail score — it indicates how strongly an entry resonates with the profile and inquiry right now. A high percentage means "look here", not "something is wrong". The entry's own text, its database, and its potency band tell you what kind of attention it is asking for.
Do I need the medical databases to analyse a business question?
No. For organizational work you select databases suited to the inquiry — business, coaching, personality development, quality management, marketing and similar. Choosing databases whose language your team understands is one of the most important decoding decisions you make.
Can I learn to decode TimeWaver outputs myself?
Yes — decoding is a trainable competency, not a gift. Our corporate Foundations training takes a team from raw result lists to confident readings in four sessions, and the open quarterly cohort teaches the same curriculum per seat. The method: read the entry's own words, locate its database context, weigh relevance and potency, then convert its vocabulary into open questions the room can answer.
Is TimeWaver a diagnostic instrument?
No. TimeWaver is used in this work as a consciousness and information-field support tool. It is not presented as a conventional diagnostic instrument or a replacement for medical, psychological, legal, or financial advice.
The TimeWaver Field Notes
Before you go — take the Field Notes with you
Occasional field notes from real trainings — decoding techniques, honest research notes, and first access to quarterly cohort seats and session openings.
By joining, you agree to receive the TimeWaver Field Notes by email. Unsubscribe anytime.