Author: RESERVE

The design goals of RESERVE have always been straightforward: provide intuitive wrappers around the FRED® API while extending those capabilities with pipeline processing and analytical tooling in a single command-line environment. Rather than forcing users to stitch together multiple utilities, scripts, and output formats, RESERVE is designed as an integrated economic data workbench where retrieval, transformation, and analysis can occur within a consistent workflow.

Early releases focused on establishing reliable access to economic data. Version 1.1.4 represents a further step toward the broader vision—making multi-series analysis a first-class workflow rather than an afterthought.

• Installing the CLI.
• Managing local data.
• Handling permissions and citations.
• Keeping installations current.

Those capabilities remain essential, but they are ultimately in service of a larger goal: helping users analyze economic data.

Version 1.1.4 takes an important step in that direction by improving how RESERVE works with multiple series at once and refining the workflows used by both humans and AI assistants.

The result is a release focused less on individual commands and more on how analysis actually happens.

Economic Analysis Is Usually Comparative

Very few macroeconomic questions can be answered by looking at a single series in isolation.

How does inflation compare to wage growth?

How does unemployment compare to labor force participation?

How do interest rates relate to housing activity?

The most useful analysis often begins with multiple series observed across the same time window.

Version 1.1.4 improves support for exactly these workflows.

Multi-Series Summaries

The headline addition is:

reserve analyze summary --by-series

reserve analyze summary --by-series

This new mode allows RESERVE to summarize multi-series JSONL streams on a per-series basis.

Rather than treating a collection of observations as a single aggregate stream, RESERVE can now preserve series-level context during analysis.

That distinction becomes increasingly important as users move from retrieving data toward comparing and interpreting it.

The feature is backed by new grouped JSONL support in the pipeline layer, allowing multi-series observation streams to flow through analysis commands in a more structured and predictable way.

Promoting Better Retrieval Patterns

One lesson that emerged from onboarding and user workflows is that many analyses begin with several related series collected over the same observation window.

Version 1.1.4 updates onboarding guidance and examples to encourage this pattern directly.

Instead of retrieving series one at a time, users are now guided toward batched requests:

reserve obs get CPIAUCSL UNRATE FEDFUNDS

reserve obs get CPIAUCSL UNRATE FEDFUNDS

followed by analysis operations such as:

reserve analyze summary --by-series

reserve analyze summary --by-series

This workflow reduces friction, keeps time windows aligned, and produces cleaner comparative analysis.

In short, it reflects how economic questions are typically explored in practice.

Improving the LLM Experience

As more users incorporate RESERVE into AI-assisted workflows, onboarding content has become increasingly important.

Prior versions attempted to expose a large portion of the command surface during onboarding.

While comprehensive, this often created unnecessary noise.

Version 1.1.4 shifts toward a more focused approach.

The default onboarding experience now provides a concise routing brief instead of a complete command catalog.

Topic-oriented guidance has also been streamlined to emphasize workflows rather than command memorization.

This makes onboarding more approachable for both human users and language models that need to understand the structure of the tool quickly.

Correctness Matters

Several fixes in this release address situations where RESERVE was being overly permissive.

Invalid global options now fail immediately rather than silently falling back to defaults.

Configuration validation has been strengthened to reject malformed values and unsupported settings.

Unknown output formats now produce explicit errors.

Malformed configuration files now surface problems instead of being ignored.

These changes may seem small, but they improve trust in the system.

When software accepts invalid input without warning, users can easily develop incorrect assumptions about how it behaves.

Failing fast makes problems easier to identify and easier to fix.

Protecting Machine-Readable Workflows

One of the more important operational improvements in this release involves structured output.

Commands such as:

• JSON
• JSONL
• CSV
• TSV
• Markdown

are frequently consumed by scripts, pipelines, and AI systems.

Version 1.1.4 now routes warnings and informational footers to stderr rather than stdout when structured formats are requested.

This preserves machine-readable output while still allowing users to see warnings and diagnostics.

For automation-heavy workflows, this distinction is critical.

Data should remain data.

Diagnostics should remain diagnostics.

A Shift Toward Workflow Design

The broader theme of v1.1.4 is not a single command.

It’s workflow design.

The release encourages users to think in terms of:

• Multiple related series
• Shared observation windows
• Structured analytical pipelines
• Machine-readable outputs
• Clear and validated configuration

Those concepts are foundational to serious economic analysis.

As RESERVE continues to evolve, that perspective becomes increasingly important.

The goal is no longer simply retrieving economic data.

The goal is helping users move efficiently from data retrieval to insight.

Version 1.1.4 is an important step in that direction.

As software matures, one of the most important questions shifts from:

“What can it do?”

to

“How easily can it stay current, healthy, and operational?”

RESERVE v1.1.3 is focused on answering that second question.

While this release doesn’t introduce new macroeconomic analysis capabilities, it lays important groundwork for long-term maintainability through self-updating infrastructure, improved cache visibility, and stronger release plumbing.

These changes are largely operational by design.

Their purpose is to make managing RESERVE simpler as the project continues to grow.

The First Step Toward Self-Updating

The headline feature in v1.1.3 is the introduction of:

reserve update apply

reserve update apply

for macOS and Linux installations.

Until now, RESERVE could tell users when a newer version existed through:

reserve update check

reserve update check

but the installation process remained manual.

Version 1.1.3 introduces the first phase of an integrated update workflow, allowing RESERVE to retrieve and apply new releases directly.

This is foundational infrastructure that will support a smoother upgrade experience moving forward.

Safe Testing for the Update Path

Updating software is one of the highest-risk operations any application performs.

To support validation and troubleshooting, RESERVE now includes a dry-run mode:

reserve update apply --dry-run

reserve update apply --dry-run

This allows users to exercise the entire update workflow—from manifest retrieval through asset resolution—without replacing the installed binary.

For developers and power users, this provides confidence that the update path is functioning correctly before any changes are made.

Combined with:

reserve update apply --dry-run --force

reserve update apply --dry-run --force

the complete update process can be tested even when the installed version already matches the latest available release.

The result is a safer and more observable update experience.

Platform-Specific Behavior Matters

Different operating systems have different expectations around software updates.

Rather than attempting a fragile in-place update workflow on Windows, RESERVE now resolves and displays the exact release asset URL required for manual installation.

This keeps behavior predictable while avoiding platform-specific edge cases that could negatively affect reliability.

The goal is not to force identical behavior across operating systems.

The goal is to provide the most reliable experience for each platform.

Making the Local Cache Easier to Understand

RESERVE’s local cache continues to play an important role in performance, offline workflows, and operational resilience.

Version 1.1.3 introduces:

reserve cache path

reserve cache path

which displays the active local database location.

While simple, this command eliminates guesswork when troubleshooting installations, inspecting local state, or working across multiple environments.

Understanding where data lives is often the first step toward understanding how a system behaves.

Better Visibility Into Local Storage

This release also expands cache diagnostics through enhanced statistics reporting.

The updated:

reserve cache stats

reserve cache stats

command now includes:

• Database schema version
• On-disk database size
• Per-bucket row counts
• Per-bucket storage consumption

These additions provide a more complete operational picture of local storage and make it easier to understand how cached data evolves over time.

As RESERVE accumulates more metadata, permissions information, observations, and local indexes, visibility into storage becomes increasingly important.

Strengthening the Foundation

Most users will not install v1.1.3 because they need a specific new economic data command.

They will install it because it makes the platform itself stronger.

• Self-update infrastructure.
• Safer release validation.
• Better platform-aware behavior.
• Improved cache visibility.
• Stronger operational tooling.

These improvements may not be the most visible features in the project, but they are the kind of investments that make future features easier to deliver and easier to maintain.

Building Toward a More Self-Sufficient Tool

The broader theme of v1.1.3 is autonomy.

RESERVE can now do more to understand its own state, manage its own lifecycle, and help users maintain healthy installations.

That’s not a new macroeconomic capability.

It’s something just as important.

It’s the beginning of RESERVE becoming a tool that not only helps users manage data—but increasingly helps manage itself.

Most people know FRED as one of the best sources for economic and financial data.

What is less obvious is that FRED is often a distributor, not the original producer.

Behind many of the series available through FRED are government agencies, statistical organizations, central banks, research institutions, exchanges, and private data providers that invest significant effort into collecting, validating, and publishing data. FRED makes that information easier to discover and consume, but the rights and usage requirements attached to the underlying data do not disappear simply because the data is accessible through an API.

As RESERVE has matured, it became increasingly important to recognize that reality.

Version 1.1.2 introduces the first comprehensive permissions and compliance framework within RESERVE.

Respecting the Source

Good data stewardship starts with acknowledging where data comes from.

Many FRED series are effectively public-domain resources. Others request attribution. Some require citation. Others may require prior approval before redistribution or use in certain contexts.

Historically, these distinctions were easy for users to overlook because the focus naturally falls on retrieving observations and performing analysis.

RESERVE now treats rights metadata as a first-class concern.

The goal is simple: help users understand and respect the requirements associated with the data they consume.

Introducing Rights-Aware Access

Version 1.1.2 adds rights and permissions classification for FRED series metadata, including support for:

• Copyrighted series requiring pre-approval
• Copyrighted series requiring citation
• Public-domain series where citation is requested
• Ambiguous or unknown rights situations

Rather than assuming every series can be treated identically, RESERVE now evaluates available rights information and responds accordingly.

When a series requires prior authorization—or when rights information is insufficiently clear—RESERVE can block access and explain why.

That behavior is intentional.

When rights are uncertain, the safest assumption is not unrestricted use.

Citations Now Travel with the Data

One of the biggest changes in this release is citation-aware output.

Required or requested citation information now flows through RESERVE output formats:

• Citation footers in table output
• Citation fields in JSON output
• Citation text columns in CSV exports

This means attribution information remains attached to the data as it moves between workflows, scripts, reports, and downstream systems.

Instead of treating citations as documentation that users must remember to revisit later, RESERVE keeps attribution closer to the data itself.

Supporting Authorized Access

Not every restricted series should be blocked forever.

Many users legitimately obtain permission to work with copyrighted or restricted datasets.

To support those workflows, RESERVE now includes a local authorization model:

reserve config grant <SERIES_ID>
reserve config revoke <SERIES_ID>
reserve config list-grants

reserve config grant <SERIES_ID>
reserve config revoke <SERIES_ID>
reserve config list-grants

These commands allow users to explicitly manage locally authorized series while preserving the broader protections introduced by the permissions framework.

The result is a system that balances compliance with practical usability.

Rights Metadata Is Part of the Cache

Permissions are only useful if they remain consistent and available.

Version 1.1.2 introduces local persistence for rights metadata, including support for rebuilding and refreshing the local rights index.

A new cache backfill reset workflow allows users to rebuild rights metadata cleanly when needed:

reserve cache reset-backfill

reserve cache reset-backfill

This ensures compliance information remains available even when working from cached datasets.

Improving Cache Reliability

Alongside permissions work, this release includes significant improvements to cache management and observation retrieval.

RESERVE now:

• Selects the widest available observation set when multiple local variants exist
• Warns when multiple cached versions of the same series are present
• Provides richer cache inventory reporting
• Supports targeted cache cleanup by series
• Improves visibility into metadata coverage and local data quality

These changes help make local data management more predictable while reducing ambiguity about which observations are being used.

Building Trust Through Transparency

Software often focuses on making data easier to access.

This release focuses on making data easier to use responsibly.

The addition of rights-aware access controls, citation propagation, permissions management, and rights metadata persistence represents an important step in RESERVE’s evolution.

Not because it unlocks a new analytical capability.

Because it acknowledges an important reality: economic data has producers, owners, and usage expectations.

Good tooling should help users respect those relationships.

Version 1.1.2 is RESERVE’s first major investment in that principle.

And it will continue to shape how the platform evolves moving forward.

The most valuable releases aren’t always the ones with the biggest feature lists.

Sometimes the best improvements are the ones that remove friction, make behavior more predictable, and help users understand what’s happening under the hood.

That’s the focus of RESERVE v1.1.1.

This release sharpens onboarding, improves cache management, and reduces the footprint of distributed binaries—small changes individually that add up to a smoother day-to-day experience.

Better Guidance for AI-Powered Workflows

As RESERVE continues to evolve alongside modern AI and LLM tooling, helping users get started quickly becomes increasingly important.

Version 1.1.1 expands onboarding guidance with richer AI and LLM-focused instructions, making it easier to understand how RESERVE fits into data exploration and analysis workflows from the very beginning.

Good tooling isn’t just about functionality—it’s about helping users discover the functionality that’s already there.

More Visibility into Local Data

Caching is one of those features users rarely think about until they need to.

To improve transparency, RESERVE now includes a cache inventory command that provides visibility into locally stored observation data and related artifacts.

Instead of wondering what’s being stored, users can now inspect cache contents directly and make informed decisions about cleanup and maintenance.

Safer Cache Cleanup

Managing cached data becomes more important as projects grow and observation sets accumulate.

Version 1.1.1 introduces a new:

reserve cache clear --series <ID>

reserve cache clear --series <ID>

workflow that allows targeted cleanup of cached data for specific series.

This release also improves handling of situations where multiple cached observation sets exist, helping prevent accidental cleanup mistakes and making cache operations more predictable.

The goal is simple: give users more control while reducing opportunities for confusion.

Clearer Inventory Reporting

Data quality and completeness matter.

When working with daily series, inventory reports will now display n/a for GAPS values when gap calculations aren’t applicable.

It’s a small change, but one that makes inventory output easier to interpret and avoids implying that missing values represent actual calculated gaps.

Smaller Downloads, Faster Installs

Not every improvement is visible from inside the CLI.

Release binaries are now stripped during the build process, reducing download sizes and improving distribution efficiency across supported platforms.

Smaller binaries mean faster downloads, lighter releases, and a more streamlined installation experience.

A Release Focused on Polish

Version 1.1.1 continues a theme established in earlier releases: investing in the quality of the overall experience.

• Better onboarding.
• More transparent cache management.
• Safer cleanup workflows.
• Clearer reporting.
• Smaller binaries.

None of these changes redefine what RESERVE can do.

Together, they make it easier to use every day—and that’s often where the most meaningful improvements happen.

When people look at software releases, it’s easy to focus on the headline features. New commands, new integrations, new capabilities.

But the earliest releases of RESERVE CLI were focused on something more fundamental: creating a tool that users can install, trust, and grow with.

From Preview to Production

The public preview release (v1.0.6) was about validating the core idea behind RESERVE. We wanted to get the CLI into people’s hands, gather feedback, and prove that the workflow was useful.

The next milestone, v1.0.9, marked the first stable public release. While it didn’t introduce flashy new functionality, it delivered something arguably more important:

• Cross-platform distribution builds
• Installation support
• Improved onboarding
• Better overall CLI usability

These improvements transformed RESERVE from a development project into software that could be reliably installed and used across environments.

The Work Nobody Notices

The v1.1.0 release continues a pattern that many infrastructure-focused projects experience early in their lifecycle: investing heavily in the parts users rarely notice when everything is working correctly.

This release introduces:

Update Awareness

A new reserve update check command provides lightweight version checking so users can quickly determine whether they’re running the latest release.

Keeping software current should be simple, and this lays the groundwork for a better upgrade experience as the project grows.

Better Configuration Management

One of the most important improvements in v1.1.0 is a more mature approach to configuration.

RESERVE now supports per-user configuration locations across macOS, Linux, and Windows while also allowing local ./config.json files to override user settings when needed.

This creates a cleaner separation between personal configuration and project-specific development workflows.

Modern Tooling

Under the hood, RESERVE now targets Go 1.26.1 and includes updated dependencies across the project.

Most users will never directly notice these upgrades, and that’s exactly the point.

Modern tooling improves reliability, maintainability, performance, and long-term sustainability without requiring users to change how they work.

Building Before Scaling

There’s a temptation in every software project to chase features.

The first releases of RESERVE have intentionally focused on something different: establishing the foundation needed to support future growth.

• Reliable installation.
• Predictable configuration.
• Version awareness.
• Modern tooling.
• Clear documentation.

These are the investments that make future features possible.

As RESERVE continues to mature, future releases will increasingly focus on expanding capabilities. But these early versions represent an important phase in the project’s evolution: turning an idea into a dependable tool.

And that’s exactly what these first releases were designed to accomplish.