context-bootstrap

To set up GRC reporting context, you must verify required setup by checking plugin presence, establishing a findings cache, and ensuring framework metadata is available before attempting to generate reports. This bootstrap process guides initial data collection and gap assessment across connectors.

Context paths are distinct bootstrap workflow routes determined by existing toolkit state. Complete path proceeds to reporting, Partial path requires additional data collection, and Empty path initiates full installation and gap assessment before generating any reports.

Report commands fail or generate hollow output during initial setup because the toolkit lacks sufficient context. The bootstrap process detects missing findings, frameworks, or history, then guides installation and first collection rather than generating incomplete reports.

Yes, week-over-week metrics require sufficient history depth to exist within the toolkit. The bootstrap process explicitly verifies that adequate historical data is present before allowing reporting commands to execute successfully.

Yes, GitOps state can be optionally checked during the reporting context bootstrap process. This optional verification occurs alongside required checks for plugin installation, findings cache, framework metadata, and history depth.

The best way is following the explicit empty-context setup script: add the marketplace, install minimum required plugins, configure a connector, collect initial findings, and run a gap assessment before attempting any report generation.