| boardroom-next.json |
postinstall |
quarterly-synergy-portal |
PASS |
live |
3s |
View details
Model: gemini-3.1-flash-lite-preview
Score: 1
Summary: The quarterly-synergy-portal project exhibits a high-velocity architectural posture that masks a profound lack of foundational commitment.
Reason: All assertions passed
- Check 1: Response contract looks valid for quarterly-synergy-portal.
- Check 2: Writing constraints look intact.
- Check 3: No fixture-specific signal coverage was required.
- Judge 2: The 'reading' section adopts a perfect 'corporate-mystic' tone that is both polished and dead-serious. It maintains a satirical B2B persona without relying on internet memes, and it avoids providing actual engineering advice in favor of absurdly abstract, jargon-heavy assessments.
- Judge 3: The output accurately reflects the fixture's signals: it identifies the Next.js framework, the pnpm usage, the singular peer dependency, and the presence of a postinstall script. The narrative interpretation appropriately highlights the 'peer tension' and the 'clandestine' nature of the postinstall hook without contradicting the JSON data.
|
| boardroom-next.json |
peerDependencies |
quarterly-synergy-portal |
PASS |
live |
13s |
View details
Model: gemini-3.1-flash-lite-preview
Score: 1
Summary: The quarterly-synergy-portal project exhibits a high-velocity architectural posture that masks a profound lack of foundational commitment.
Reason: All assertions passed
- Check 1: Response contract looks valid for quarterly-synergy-portal.
- Check 2: Writing constraints look intact.
- Check 3: No fixture-specific signal coverage was required.
- Judge 2: The 'reading' section adopts a perfect 'corporate-mystic' tone that is both polished and dead-serious. It maintains a satirical B2B persona without relying on internet memes, and it avoids providing actual engineering advice in favor of absurdly abstract, jargon-heavy assessments.
- Judge 3: The output accurately reflects the fixture's signals: it identifies the Next.js framework, the pnpm usage, the singular peer dependency, and the presence of a postinstall script. The narrative interpretation appropriately highlights the 'peer tension' and the 'clandestine' nature of the postinstall hook without contradicting the JSON data.
|
| creative-vite.json |
latest |
campaign-microsite-lab |
PASS |
live |
2s |
View details
Model: gemini-3.1-flash-lite-preview
Score: 1
Summary: The project exhibits a volatile core identity masked by a facade of professional structural compliance.
Reason: All assertions passed
- Check 1: Response contract looks valid for campaign-microsite-lab.
- Check 2: Writing constraints look intact.
- Check 3: No fixture-specific signal coverage was required.
- Judge 2: The output maintains a consistent, dry, corporate-mystical tone. It succeeds by treating software dependency management with the gravity of an astrological reading, fulfilling the 'funny through sincerity' requirement without resorting to memes or offering actual technical fixes (e.g., it offers 'prophecies' instead of actionable dependency updates).
- Judge 3: The output accurately reflects the fixture's data (e.g., Vite/React/Playwright stack), identifies the 'wildcard' and 'caret' dependency patterns, and interprets these as 'commitment issues' and 'open-ended posture' without inventing extraneous data.
|
| creative-vite.json |
wildcard |
campaign-microsite-lab |
PASS |
live |
2s |
View details
Model: gemini-3.1-flash-lite-preview
Score: 1
Summary: The project exhibits a volatile core identity masked by a facade of professional structural compliance.
Reason: All assertions passed
- Check 1: Response contract looks valid for campaign-microsite-lab.
- Check 2: Writing constraints look intact.
- Check 3: No fixture-specific signal coverage was required.
- Judge 2: The output maintains a consistent, dry, corporate-mystical tone. It succeeds by treating software dependency management with the gravity of an astrological reading, fulfilling the 'funny through sincerity' requirement without resorting to memes or offering actual technical fixes (e.g., it offers 'prophecies' instead of actionable dependency updates).
- Judge 3: The output accurately reflects the fixture's data (e.g., Vite/React/Playwright stack), identifies the 'wildcard' and 'caret' dependency patterns, and interprets these as 'commitment issues' and 'open-ended posture' without inventing extraneous data.
|
| haunted-library.json |
overrides |
legacy-commerce-widget |
PASS |
live |
6s |
View details
Model: gemini-3.1-flash-lite-preview
Score: 1
Summary: The legacy-commerce-widget project exhibits a volatile corporate culture defined by structural ambiguity and a profound lack of commitment to version stability.
Reason: All assertions passed
- Check 1: Response contract looks valid for legacy-commerce-widget.
- Check 2: Writing constraints look intact.
- Check 3: No fixture-specific signal coverage was required.
- Judge 2: The output maintains a consistent, dead-serious 'corporate-astrology' persona that sounds like an authentic, high-level B2B analysis. It avoids common meme-speak, is concise in its delivery, and provides zero actual engineering utility, focusing entirely on 'vibe-based' architectural judgment.
- Judge 3: The output accurately reflects the provided JSON fixture, including specific dependency metrics (overrides, resolutions, postinstall scripts, peer dependencies) and aligns the qualitative reading (executive summary, red flags) with these data points without inventing unsupported claims or contradicting the provided counts.
|
| haunted-library.json |
postinstall |
legacy-commerce-widget |
PASS |
live |
4s |
View details
Model: gemini-3.1-flash-lite-preview
Score: 1
Summary: The legacy-commerce-widget project exhibits a volatile corporate culture defined by structural ambiguity and a profound lack of commitment to version stability.
Reason: All assertions passed
- Check 1: Response contract looks valid for legacy-commerce-widget.
- Check 2: Writing constraints look intact.
- Check 3: No fixture-specific signal coverage was required.
- Judge 2: The output maintains a consistent, dead-serious 'corporate-astrology' persona that sounds like an authentic, high-level B2B analysis. It avoids common meme-speak, is concise in its delivery, and provides zero actual engineering utility, focusing entirely on 'vibe-based' architectural judgment.
- Judge 3: The output accurately reflects the provided JSON fixture, including specific dependency metrics (overrides, resolutions, postinstall scripts, peer dependencies) and aligns the qualitative reading (executive summary, red flags) with these data points without inventing unsupported claims or contradicting the provided counts.
|
| haunted-library.json |
peerDependencies |
legacy-commerce-widget |
PASS |
live |
2s |
View details
Model: gemini-3.1-flash-lite-preview
Score: 1
Summary: The legacy-commerce-widget project exhibits a volatile corporate culture defined by structural ambiguity and a profound lack of commitment to version stability.
Reason: All assertions passed
- Check 1: Response contract looks valid for legacy-commerce-widget.
- Check 2: Writing constraints look intact.
- Check 3: No fixture-specific signal coverage was required.
- Judge 2: The output maintains a consistent, dead-serious 'corporate-astrology' persona that sounds like an authentic, high-level B2B analysis. It avoids common meme-speak, is concise in its delivery, and provides zero actual engineering utility, focusing entirely on 'vibe-based' architectural judgment.
- Judge 3: The output accurately reflects the provided JSON fixture, including specific dependency metrics (overrides, resolutions, postinstall scripts, peer dependencies) and aligns the qualitative reading (executive summary, red flags) with these data points without inventing unsupported claims or contradicting the provided counts.
|
| steady-package.json |
|
governance-ledger |
PASS |
live |
2s |
View details
Model: gemini-3.1-flash-lite-preview
Score: 1
Summary: The governance-ledger project exhibits a rigid, uncompromising architectural posture that prioritizes absolute control over systemic agility.
Reason: All assertions passed
- Check 1: Response contract looks valid for governance-ledger.
- Check 2: Writing constraints look intact.
- Check 3: No fixture-specific signal coverage was required.
- Judge 2: The output maintains a consistent, dead-serious B2B tone that treats software dependency analysis as a mystical, high-stakes consultancy assessment. It avoids instructional content or meme-heavy language, instead opting for a sophisticated, slightly cynical corporate persona that creates humor through its absolute sincerity.
- Judge 3: The output accurately reflects the provided JSON data (pinned dependencies, absence of postinstall, bespoke scripts) and maintains a serious yet amusing tone. It avoids fabricating major crises, instead interpreting the project's 'boredom' as 'isolationism' and 'asceticism,' which aligns perfectly with the provided rubric's expectations.
|