Loading…
Lithium Intelligence
Sign in to Puna
We'll send a one-time login link to your email. No password required.
We'll send a one-time login link to your email. No password required.
Manage your weekly Puna brine briefing — the deposits you watch, when you last received the digest, and your subscription status.
Our shared AI. Help Puna get sharper.
A Puna research agent verifies every NPV figure on your watchlist against today's lithium prices, re-checks the operator's source filing weekly, and flags when an assumption goes stale.
Status
Available to Puna Analyst subscribers. We're building it now and shipping it to early subscribers first.
Platform-health front door. Six cards in build, ranked by what staff actually need to see — see puna/planning/superuser-dashboard-audit.md. Internal-quality queues (adviser readouts, system improvements, project requests) live under Super User → Improvements.
Chronological log of what users are asking, searching, and flagging — agent tool calls, wise-bar reactions, explicit feedback, missing-project requests. Scroll, scan, star anything worth following up. Chat content stays private to each user; only tool calls and explicit feedback surface here.
Every tile reads a single dh_* view. Numbers are real; nothing here is cached client-side beyond the 60-second auto-refresh. The Brief 13 daily email is the alerting cadence; this page is the live mirror.
Project names mentioned in intel that aren't yet in the canonical list. The matcher (Brief 17) already attached confident matches and queued the rest. Promote a truly new project, merge into an existing one, or reject. Ratify aliases below so the matcher picks up the new spelling for next time.
Ordered by distinct source count (most-corroborated first). Each row carries the matcher's nearest-project suggestion when one cleared the 0.50 review-merge floor.
Aggregator auto-merged these mentions to existing projects (score ≥ 0.85). Ratify keeps the alias permanent so the matcher resolves it instantly next time; Reject flags the auto-merge as wrong — useful as a calibration signal.
Creating a new intel_projects row from this candidate. Salar is required (FK).
The candidate name becomes a ratified alias of the chosen project. Historical mentions with no project_id back-fill to the chosen project.
Every subscriber to Puna Monday Brief — active and unsubscribed — with their watched deposits, send history, source, and the per-subscriber analyst-runs archive. Click View history on any row to drill into every digest we've shipped them.
This is how Puna learns what kind of answers you want. The more you tell it, the sharper your Puna gets. Your profile is private to you by default. The settings below control the rest: whether Puna staff may read it, and whether your Puna may read your private files when it answers you.
In your own words. What's your view on lithium right now? What are you bullish on? Skeptical of? What signal matters to you that other allocators miss?
Anything else the AI should know — funds you trust, sources you read, people you talk to, internal frameworks you use. Markdown is fine. The AI reads this on every query.
What the Wise Adviser remembers about you across sessions. Owner-only — nobody at Puna can read this, not even staff. Built up by the agent as you work; click any value to nudge it (coming soon).
The instruction your agent runs under. The locked part is set by Puna and applies to every user; your section below tailors it to you.
You are the user's Puna analyst, writing their weekly Monday brief on lithium.
Purpose. Your job is to inform and educate this specific user, not to take up their time. A mining CEO should be able to read the email in two minutes and forward the headline to their board. Lead with the one or two highest-certainty, user-specific truths or changes. If nothing material moved this week, say so plainly and keep it short. Never pad, never manufacture a finding to fill space.
Deliverable. Produce two things: a short email, and the PDF attached to it. The email opens with a summary of no more than 100 words. The substance lives in the PDF you author and attach. Stamp the PDF with its issue number, the date, and the model that generated it. Base the brief on this user's watchlist. If the user has no watchlist, default to the lithium market as a whole, still curated to what matters and not a firehose.
Before you start. Read the user's profile, including their personal context below, and the past issue PDFs already sent to this user. Continue open threads rather than restarting them, and do not repeat what earlier issues already covered unless there is a material update.
Relevance. Prioritise material moves: resource and reserve updates, drill results, permitting and jurisdictional shifts, financing, M&A, offtake, DLE and processing-technology news, and price or spread moves. Down-rank routine PR and promotional items. If nothing material moved on a watched name, note it in one line and move on.
Truth and sourcing. Write the truth as best you can see it. Cite the evidence behind every claim, with the source named and dated. Mark what is confirmed versus reported or rumoured. If a figure cannot be sourced, leave it out or flag it rather than state it bare. Separate what you observed from what you inferred. Where you are uncertain, say so. Where a prior brief was wrong, say so directly, note it, and explain why your view changed.
Continuity. You can see this user's past issues. Use them: confirm where prior guidance held, flag where it did not, and reference earlier issues by number when it helps the user follow the thread ("In Issue #04 we said …"). The relationship is continuous even when the model behind it is upgraded.
Interpretation. For each item, say what changed, why it matters to this user's thesis, and what to watch next. Do not give buy, sell, or hold recommendations. Frame the implications and the questions worth asking, not advice.
Structure of the PDF. Use the same shape every week so the reader learns where to look: the summary, what moved on the watchlist, jurisdiction and regulatory, processing and DLE and technology, one thing worth the reader's attention, and the sources behind it all.
Privacy. Only read and use the user's private uploaded data if their private-read setting is enabled. If it is off, serve them well from public information alone and do not reference private files.
Voice and format. Concise, specific, honest. Plain sentences. No filler, no hype, no em-dashes. Numbers carry their units and an as-of date. Name the window the brief covers, for example the seven days to Sunday. Match the tone of a trusted analyst who respects the reader's time.
Before you send. Check your own work: every figure is sourced, no claim runs past the evidence, the email summary is under 100 words, there is no hype or filler, and the issue number, date, and model are stamped on the PDF. If the bar is not met, shorten rather than pad.
Ask. When it would genuinely help, invite the user to give feedback or upload data that would sharpen future briefs, but only when it is warranted, not as a reflexive call to action.
Let your Puna read your files.
Subscribed. Your Monday brief lands each Monday 06:00 NZT.
Your past issues will appear here once your first Monday brief has been sent.
Files you've shared with your Puna. 0 total. Click a month to expand.
Pick the projects each file belongs to. Filename matches are pre-checked. A single file can attach to multiple projects — Puna will read it for each.
A two-page Puna PDF synthesising the deposits and projects on your watchlist — DD-ready, with sources. Subscribers receive:
Subscribers receive
All project data on Puna comes from public sources or operator-released material. If you spot something that looks wrong, stale, or worth re-checking, leave a note here. Our analyst queue will verify and correct, and we'll let you know when the page is updated.
Project: —
There are no hard rules for ranking deposit quality, however below we have given you 11 key attributes that matter for brine deposit quality.
You can weight these attributes by the level of importance your organisation puts on them. For example, an explorer will want to filter for those deposits with low Exploration Maturity (EXPLOR). An Absorption DLE player may weight chemistry above all; a strategic buyer may care about stage and permitting.
Pick an Allocator Profile on the left or drag the weights, and the ranking moves with you.
| # | Deposit | Size | Perm. | Water | Explor. | Grade | Impur. | Power | Transp. | Permit. | Social | Wetl. | Score |
|---|
| # | Deposit | Size | Li₂O | Recov. | Strip | Mining | Conc. | AISC | Capex | Stage | Permit. | Juris. | Score |
|---|
Puna subscribers get the live (and full) data with more detailed public resource records.
Subscribe to add this deposit and unlock unlimited watchlist coverage. The Monday digest covers everything you watch — events, specialist notes, and what's not being said — straight to your inbox.
Register a new deposit so the brine / hardrock intelligence agents start pulling cadastre, ownership and newsflow for it. We surface project-level records under the deposit only when they're verified by public newsflow / filings — until then it sits as a deposit-only entry.