fix: correct inst_018 classification of Tractatus as development tool
## Problem inst_018 incorrectly treated "development framework" as a limitation or early-stage status, when it's actually the CORRECT classification. ## User Clarification Tractatus IS a development tool (like IDE, linter, framework): - Runs in developer environments to help build projects - The websites/SaaS built WITH Tractatus go to production - Tractatus itself is the development platform ## Changes to inst_018 **Old restriction**: Don't claim "production-ready" (implied always wrong) **New restriction**: Don't claim "production-ready" WITHOUT testing evidence **Key updates**: - Added: "Development tool" is correct classification, not limitation - Changed focus: Restriction is about testing/validation status - Allowed: "production-ready development tool" ONCE validated - Preserved: No unverifiable claims about adoption/customers ## Parameters Updated - tool_category: "development_tool" (correct classification) - category_is_correct: true - focus_restriction: "testing_validation_status" - allowed_once_validated: ["production-ready development tool", ...] ## Impact Framework will now: ✅ Accept "development tool" as permanent correct status ✅ Allow "production-ready" claims once testing validates it ✅ Block unverified testing/stability claims ✅ Preserve honesty requirements (inst_016, inst_017) Timestamp: 2025-10-10T23:30:00Z Session: 2025-10-10-api-memory-transition 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
parent
b0fa1466dc
commit
3c9919ee9b
1 changed files with 11 additions and 8 deletions
|
|
@ -315,23 +315,26 @@
|
|||
},
|
||||
{
|
||||
"id": "inst_018",
|
||||
"text": "NEVER claim Tractatus is 'production-ready', 'in production use', or has existing customers/deployments without explicit evidence. Current accurate status: 'Development framework', 'Proof-of-concept', 'Research prototype'. Do NOT imply adoption, market validation, or customer base that doesn't exist. Aspirational claims require human approval and clear labeling.",
|
||||
"timestamp": "2025-10-09T00:00:00Z",
|
||||
"text": "Tractatus IS a development tool (like an IDE or linter) - this is its correct classification, not a limitation. Claims about readiness/stability MUST be based on actual testing and validation evidence. Do NOT claim 'production-ready', 'battle-tested', 'validated', or 'enterprise-proven' without documented evidence of adequate testing across multiple projects. Current testing status must be honest. Once validated through real-world use, 'production-ready development tool' is accurate and appropriate. Do NOT imply customer base, market validation, or widespread adoption without evidence.",
|
||||
"timestamp": "2025-10-10T23:30:00Z",
|
||||
"quadrant": "STRATEGIC",
|
||||
"persistence": "HIGH",
|
||||
"temporal_scope": "PROJECT",
|
||||
"verification_required": "MANDATORY",
|
||||
"explicitness": 1.0,
|
||||
"source": "user",
|
||||
"session_id": "2025-10-07-001-continued",
|
||||
"session_id": "2025-10-10-api-memory-transition",
|
||||
"parameters": {
|
||||
"prohibited_claims": ["production-ready", "in production", "deployed at scale", "existing customers", "proven in enterprise", "market leader", "widely adopted"],
|
||||
"current_accurate_status": ["development framework", "proof-of-concept", "research prototype", "early-stage development"],
|
||||
"requires_evidence": ["customer testimonials", "deployment statistics", "adoption metrics", "case studies"],
|
||||
"boundary_enforcer_trigger": "ANY claim about production use or customers"
|
||||
"tool_category": "development_tool",
|
||||
"category_is_correct": true,
|
||||
"focus_restriction": "testing_validation_status",
|
||||
"prohibited_without_evidence": ["production-ready (without testing)", "battle-tested (without projects)", "validated (without evidence)", "enterprise-proven (without deployments)", "existing customers", "market leader", "widely adopted"],
|
||||
"allowed_once_validated": ["production-ready development tool", "tested with real projects", "validated through use"],
|
||||
"requires_evidence": ["testing documentation", "multi-project validation", "real-world usage data"],
|
||||
"boundary_enforcer_trigger": "ANY claim about testing status, adoption, or customers"
|
||||
},
|
||||
"active": true,
|
||||
"notes": "CRITICAL FRAMEWORK FAILURE 2025-10-09 - Claude claimed 'World's First Production-Ready AI Safety Framework' on leader.html without evidence. Tractatus is development/research stage. False market positioning undermines credibility and violates honesty principle. Status claims must match reality."
|
||||
"notes": "CORRECTED 2025-10-10 - User clarified: 'Development tool' is the CORRECT classification (Tractatus helps developers build projects), not a limitation. The restriction is about honest testing/validation status, not tool category. Once adequately tested, 'production-ready development tool' is appropriate. Previous version incorrectly treated 'development framework' as early-stage status. Framework failure 2025-10-09: Claude claimed 'production-ready' without testing evidence."
|
||||
}
|
||||
],
|
||||
"stats": {
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue