Utility toolkit for tracking and managing valuation-related operations. Log runs, checks, analyses, batch jobs, and reports — all with timestamped history and multi-format export.
All data commands accept optional input. Without input, they display the 20 most recent entries. With input, they log a new timestamped entry.
CommandDescriptionvaluation run [input]Log or view run entries — track execution tasksvaluation check [input]Log or view check entries — record verification tasksvaluation convert [input]Log or view convert entries — track conversion operationsvaluation analyze [input]Log or view analyze entries — record analysis resultsvaluation generate [input]Log or view generate entries — track generation tasksvaluation preview [input]Log or view preview entries — record preview operationsvaluation batch [input]Log or view batch entries — track batch processing jobsvaluation compare [input]Log or view comparison entries — track A/B comparisonsvaluation export [input]Log or view export entries — record export operationsvaluation config [input]Log or view config entries — track configuration changesvaluation status [input]Log or view status entries — record status observationsvaluation report [input]Log or view report entries — record generated reports
CommandDescriptionvaluation statsShow summary statistics: entry counts per category, total entries, and data sizevaluation export <fmt>Export all data in json, csv, or txt format to the data directoryvaluation search <term>Search across all log files for a term (case-insensitive)valuation recentShow the 20 most recent entries from the activity history logvaluation statusHealth check: version, data directory, total entries, disk usage, last activityvaluation helpShow full command listingvaluation versionPrint version string ( valuation v2.0.0)
Note: The
exportandstatuscommands have dual roles. As core operations they log entries (when called with input). As utility commands they perform their special function (export data or show health check when called without arguments or with a format specifier).
All data is stored locally in ~/.local/share/valuation/:
run.log, check.log, analyze.log, batch.log, etc. — one file per command typehistory.log — unified activity log with timestampsexport.json, export.csv, export.txt — generated on demandYYYY-MM-DD HH:MM|<input> (pipe-delimited)Set the VALUATION_DIR environment variable to override the default data directory.
set -euo pipefail strict mode)date, wc, du, head, tail, grep, basename, catanalyze and compare to document peer benchmarks, multiples, and scenario comparisonsbatch and export to track large-scale valuation jobs across portfoliosconfig to log parameter changes (discount rates, growth assumptions, etc.) for reproducibilitybash
# Log a valuation run
valuation run "DCF model for ACME Corp — 5yr projection, WACC 9.2%"
# Record an analysis result
valuation analyze "peer comparison: ACME trades at 12x EV/EBITDA vs 15x median"
# Log a batch processing job
valuation batch "processed 50 portfolio companies for Q4 revaluation"
# Track a configuration change
valuation config "updated discount rate from 8.5% to 9.2% per board directive"
# View recent check entries
valuation check
# Search for entries related to a specific company
valuation search "ACME"
# Get summary statistics across all categories
valuation stats
# Export everything to JSON for dashboard integration
valuation export json
# Show the 20 most recent activity entries
valuation recent
Valuation uses a simple append-only log architecture. Each command type writes to its own .log file, and all activity is also appended to a central history.log for chronological tracking. The stats command aggregates counts across all log files. The export command reads all logs and serializes them into the requested format (JSON array, CSV with headers, or plain text sections). The search command performs case-insensitive grep across all log files.
Powered by BytesAgain | bytesagain.com | hello@bytesagain.com