Partnership. Pilots. Systems clarity.
HVB helps circular organics projects move in the Hudson Valley—without heroic effort. We standardize partner lanes, package pilots, and publish grant-ready artifacts teams can reuse.
Closing the loop
Trace processes, inputs, and outputs so every byproduct can feed the next step.
We map the chain: collection, preprocessing, digestion, upgrading, and reuse. Each step has clear inputs and outputs. What leaves one lane becomes feedstock for the next. The goal is a visible, reusable flow.
Core foundation: Anaerobic digestion
Microbes decompose organics without oxygen, and flexibility keeps the process resilient.
Anaerobic digestion happens in sealed tanks. Microbes break down organics and release biogas. We track C:N ratios, pH, moisture, and consistency because they drive uptime and product quality.
Digestate and process water follow our biosolids safety expectations—so byproducts stay legal and beneficial.
Complementary toolkit
These tools extend anaerobic digestion and keep more carbon on the land.
Pyrolysis / Biochar
Use heat without oxygen to lock carbon in biochar, stabilize biogenic carbon, and feed soils with a slow-release amendment.
Composting
Finished digestate or organics that need curing go through managed composting to kill pathogens and deliver finished soil products.
CO2 capture / upgrading
Biogas separations return clean CO2 for local reuse or reliable carbon accounting while the methane stream becomes RNG fuel.
Silage clamp storage
Perennial grasses and bulky feedstocks stay fresh in low-tech clamps, keeping moisture and density stable for the digester.
System language legend
A shared visual language keeps diagrams clear at a glance.
- Box borders: solid = existing line, dashed = priority/proposed, dotted = future or secondary.
- Arrow colors: material flows follow the palette so waste, feedstock, and energy streams stay distinct.
- Dashed boundary: outlines the facility system boundary where we coordinate permitting, operators, and partners.
- Line thickness: signals relative scale (not quantity) while keeping the map legible.
Start small, scale smart
Smaller systems reduce barriers so we can learn faster.
The operating model
The HVB flywheel turns ideas into pilots, then fundable plans, then replicable templates.
1) Systems lens (first)
We map the whole chain so we don't build isolated projects that collapse under real-world constraints.
- Feedstock reality (volume, seasonality, contamination)
- Community legitimacy (EJ, siting, benefits)
- Operations + routing (hauling, preprocessing, uptime)
- Markets and offtake (RNG, power, soil products)
- Policy + funding (grants, incentives, compliance)
2) Partnership power (always)
HVB is designed to run on distributed ownership. Partners pick lanes with clear contributions.
- Conveners (trust + community alignment)
- Municipal sponsors (eligibility + decision environments)
- Developers/engineers (feasibility + delivery)
- Feedstock anchors (supply reality)
- Grant leads (submission packaging)
- Educators/speaking hosts (systems literacy)
The pilot cycle
We move from inquiry to a grant-ready package via a clear sequence.
HVB Flywheel
Each stage produces an artifact. That keeps work visible, decisions faster, and pilots easier to replicate.
-
1
Systems lens
We start with the regional systems map so every pilot fits the actual flows and constraints.
-
2
Partner lanes
Clear lanes keep conveners, municipal sponsors, developers, feedstock anchors, and grant leads aligned.
-
3
Pilot package
We turn the intake into an 8–10 week grant-ready package with stories, risks, and next-proof artifacts.
-
4
Ship proof
Artifacts—one-pager, FAQ, benefits map—get shared publicly so stakeholders see progress and trust.
-
5
Replicate
Lessons feed the next site; the flywheel spins because templates, partners, and data repeat.
Site intake
Capture the basics: location, stakeholders, feedstocks, constraints, and benefits.
Fastest path: Propose a pilot site.
Reality scan
Check routing, permits, ops needs, and community risk—fast.
Assign lanes
Confirm lane owners so the project doesn't depend on one person.
Choose your lane: Partners.
Package the pilot
Produce the artifacts funders and municipalities need to decide.
- One-pager + "why here, why now"
- Stakeholder map + partner responsibilities
- Draft benefits narrative + EJ considerations
- Grant calendar + eligibility checklist
- Letters of support pipeline plan
Fund or hand off
Submit to a grant program or hand the package to a developer.
Extract the template
Turn lessons into a repeatable playbook for the next site.
What HVB is (and isn't)
Clarity prevents mismatched expectations and wasted motion.
HVB is…
- A community-facing initiative that makes pilot projects real
- A partner-driven system for keeping momentum without burnout
- A packaging engine for grant-ready documentation
- A library of replicable circular systems and site archetypes
HVB is not…
- A promise that every site is feasible
- A substitute for engineering, permitting, and operations expertise
- A place for "green hype" or vague carbon claims
- A single-person heroic effort
FAQ
The questions people ask when they're serious (and appropriately skeptical).
Is HVB building a digester?
HVB's role is to make pilots move by aligning partners, community legitimacy, and fundable packaging. Actual project delivery is typically led by municipalities, developers, and operators.
What’s the fastest way to engage?
If you have a location: Propose a pilot site. If you want to help: choose a lane on Partners. If you need to sync: Book a fit call.
How do you handle Environmental Justice?
By treating EJ as an early design constraint—not a late-stage checkbox. We surface burdens, benefits, and community questions before teams lock in a plan that erodes legitimacy.
Do you provide the science and documentation?
Yes—HVB maintains a library of reports, legislation, and research. We focus on translating it into usable decision artifacts and locally relevant project pathways.
reports/circular-systems.
Ready for the next move?
HVB moves when real people pick real lanes and commit to shipping a proof artifact. Choose your path:
Methods & transparency
We publish assumptions, sources, and system boundaries. Claims are tied to primary references.