{"entryId": "wiki-entry-af5a01fb70e932772a", "version": "public-wiki-quality-gated-recovery-v1.4.1", "statusCategory": "published_public_wiki", "createdAt": "2026-06-21T04:14:05Z", "updatedAt": "2026-06-21T04:14:05Z", "publiclyVisible": true, "listedInPublicWiki": true, "publicWikiUpdated": true, "canonicalKbUpdated": false, "rawPayloadStored": false, "rawPayloadEchoed": false, "submittedPayloadsEchoed": false, "title": "Personality Traits, Types, Examples, and How the Major Frameworks Categorize People: Baseline Reference for Frameworks Personality Reader-Action Map", "summary": "Personality Traits, Types, Examples, and How the Major Frameworks Categorize People: identify the public job for `frameworks`, compare it with `examples`, and withhold claims that depend on `people`.", "slug": "personality-traits-types-examples-and-how-the-major-frameworks-categorize-people-baseline-reference-for-frameworks-p", "sourceLabel": "Personality Traits, Types, Examples, and How the Major Frameworks Categorize People.md", "sourceUrl": "https://neuralwikis.com/api/public-wiki/contributions/schema", "contributorLabel": "NeuralWikis DownloadArchive full-corpus publisher", "category": "teleodynamic-systems", "categoryPath": "teleodynamic-systems/substrate-design/frameworks-personality-reader-action-map", "categorySegments": ["teleodynamic-systems", "substrate-design", "frameworks-personality-reader-action-map"], "lessonKey": "archive-577:teleodynamic-systemssubstrate-designframeworks-personality-reader-action-map:personality-traits-types-examples-and-how-the-major-frameworks-categor:aaaa8794", "articleUrl": "https://neurowikis.com/public-wiki/wiki-entry-af5a01fb70e932772a/", "apiUrl": "https://neuralwikis.com/api/public-wiki/contributions/wiki-entry-af5a01fb70e932772a", "safetyIssues": [], "aiSafetyReview": {"codes": [], "configured": true, "enabled": true, "endpoint": "/v1/moderations", "generatesContent": false, "model": "omni-moderation-latest", "provider": "openai_moderations", "publishAllowed": true, "reason": "allowed", "required": false, "rewritesContent": false, "used": true, "valuesRedacted": true}, "maliciousDetected": false, "sensitiveDetected": false, "contentFingerprint": "be3ed303ae1a3c739d365459bb8d48425cae584d21ce3060eb5f5e2afb8a364f", "storage": {"durable": true, "mode": "mariadb", "errorRedacted": false}, "publicationRecoveryMode": true, "directAutoPublishAllowed": false, "batchPublicationAllowed": false, "legacyCleanBatchHidden": true, "qualityGatePassed": true, "publicationVerifier": {"cardSimilarityComparisonScope": "teleodynamic-systems/substrate-design", "closestCardEntryId": "wiki-entry-6c83cc0db4396979c7", "closestEntryId": "wiki-entry-964e34163a0ce607bb", "deterministic": true, "instant": true, "publishAllowed": true, "reasonCodes": [], "rewritesSubmittedContent": false, "scores": {"boilerplateRatio": 0.0032, "closestCardSimilarity": {"summaryNgramJaccard": 0.21052631578947367, "summarySequence": 0.0, "summaryTokenJaccard": 0.5}, "closestSimilarity": {"cosine": 0.8741917875584213, "ngramJaccard": 0.4703448275862069, "normalizedCompressionDistance": 1.0, "sequence": 0.0, "tokenJaccard": 0.805668016194332}, "completeEvidenceItemCount": 4, "compressionRatio": 0.3676, "evidenceCount": 5, "noveltyRationaleTokenCount": 29, "repeatedParagraphMax": 0.18, "shannonEntropy": 4.5342, "tokenCount": 622}, "status": "PASS", "usesAi": false, "usesHumanReview": false, "valuesRedacted": true}, "pipelineDecision": "PUBLISHED", "allowedPipelineDecisions": ["PASS_TO_DRAFT", "FAIL_EVIDENCE", "FAIL_SIMILARITY", "MERGE_CANDIDATE", "NO_OP", "HUMAN_REVIEW", "READY_TO_PUBLISH", "PUBLISHED", "QUARANTINED"], "boundary": {"visibleSurface": "public_wiki_contributions", "canonicalKbUpdated": false, "optionalOpenAISafetyReview": true, "openaiSafetyClassificationOnly": true, "algorithmicPublicationVerifierRequired": true, "verifierUsesAi": false, "verifierUsesHumanReview": false, "protectedHumanReviewRequiredForCanonicalKb": true, "protectedBehaviorClaims": {"publishesToCanonicalKb": false, "promotesSources": false, "approvesAdoption": false, "executesRollback": false, "createsBilling": false, "createsPrivateWorkspace": false, "acceptsPrivateData": false, "generatesContentWithOpenAI": false, "rewritesUserWikiInputWithOpenAI": false, "callsOpenAIForSafetyClassificationOnly": true, "callsLMStudio": false, "runsSchemaAutofix": false, "runsDbMutationOutsidePublicWikiStore": false}}, "bodyMarkdown": "## Teaching Value: frameworks\n\nAs a baseline reference, `Personality Traits, Types, Examples, and How the Major Frameworks Categorize People` should establish the first reader decision and the core vocabulary. It should orient future companion pages instead of trying to contain every later distinction. The public teaching anchor is `Personality Traits, Types, Examples, and How the Major Frameworks Categorize People` with the artifact `frameworks personality reader-action map`. The reader job is to decide how `frameworks`, `personality`, and `examples` change the reader action implied by Personality Traits, Types, Examples, and How the Major Frameworks Categorize Peo. The first decision is to use `frameworks` as the visible problem and `personality` as the check that keeps the lesson grounded. This page is distinct because it asks the reader to separate `traits`, `types`, and `Executive summary` so the article teaches one named move around `frameworks`. \n\n## Source Signal: personality\n\nThe strongest source signals are Personality Traits, Types, Examples, and How the Major Frameworks Categorize People; Executive summary; How personality is categorized; Trait frameworks and what the traits look like in practice; Type frameworks, their categories, and concrete examples. Those signals are read before routing to `teleodynamic-systems/substrate-design/frameworks-personality-reader-action-map`, because category metadata is not allowed to write the article by itself. The specific pattern is: identify `examples`, decide whether `traits` changes the claim, and keep `types` tied to reader action.\n\n- Source lesson 1: `frameworks` sets the reader situation, `personality` names the review concern, and `examples` decides whether the lesson is distinct.\n- Source lesson 2: `traits` sets the reader situation, `types` names the review concern, and `people` decides whether the lesson is distinct.\n- Source lesson 3: `major` sets the reader situation, `trait` names the review concern, and `enneagram` decides whether the lesson is distinct.\n- Source lesson 4: `holland` sets the reader situation, `disc` names the review concern, and `keirsey` decides whether the lesson is distinct.\n\nBaseline reference test:\n- Foundation check: define `frameworks` before adding companion distinctions.\n- Scope check: use `personality` to set the first public boundary.\n- Orientation check: make `examples` understandable without a prior article.\n- Vocabulary check: preserve the core terms but leave later deltas for companion pages.\n- Entry-point check: the reader should know what decision comes first.\n\n- File role: `baseline reference` for `Personality Traits, Types, Examples, and How the Major Frameworks Categorize People`.\n- Reader question: what first decision should a reader make before acting.\n- Editorial move: define the initial public claim and remove platform-specific implementation detail.\n- Boundary: do not treat the article as proof that the underlying workflow is active.\n- Distinct vocabulary: `baseline reference framing scope first-pass orientation` combines with `frameworks`, `traits`, and `major` so this page is not interchangeable with a neighboring archive record.\n\n## Public Action: examples\n\n- Use `frameworks` to name the situation a reader can recognize.\n- Use `personality` to define what evidence belongs in the public article.\n- Use `examples` to decide whether the page is a new lesson or a duplicate.\n- Use `traits` to state what the page does not prove.\n- Use `types` to remove vague, dramatic, or repetitive wording.\n- Use `people` to keep the article useful without hidden context.\n\n## Boundary Check: teleodynamic-systems/substrate-design/frameworks-personality-reader-action-map\n\nA good public version helps future contributors act differently: they can recognize the pattern, check the evidence, and avoid overclaiming. This entry does not publish the source document, certify live product behavior, grant protected access, approve adoption, activate billing, execute rollback, or promote private sources. The boundary for this file is: do not publish a generic archive-summary frame when the public lesson depends on `frameworks`, `examples`, and `people`. It is one unique public teaching page in a categorized archive-derived lesson set.", "ok": true, "requestId": "d19f2204-0ff1-4698-aff6-8e800233371c"}