Article summary
Accept Libya +218 WhatsApp Full Format through schema version, required fields, unknown semantics and count reconciliation rather than column count.
A Libya +218 Full Format workbook with ten columns is not automatically more complete than a six-column result. Completeness depends on task contract, interpretable states and the ability to reconnect every row.
Define the schema contract first
| Item | Acceptance |
|---|---|
| schema_version | Matches the task |
| required_columns | Correct names and types |
| null_semantics | Unknown is not false |
| row_key | Stable reconnection |
Extra columns still need purpose
Avatar, skin-tone or mapping fields with no business purpose are not free information. Remove them before import or restrict access.
Validate provenance before +218
Preserve phone_raw and country_evidence. A Libya project folder does not justify prepending +218 to every row.
Use count reconciliation for row completeness
submitted, returned, format_exception and task_unknown must close. Explain every extra or missing row.
Score field families separately
Base/activity, profile observation and account relationship each report usable and unknown. One family cannot improve another’s score.
Keep TXT execution-only
Upload one phone per line while name, order and permission stay in the private crosswalk. Split access after Excel reaches staging.
A mapping is not a “complete customer”
A mapped phone requires time and conflict review. It cannot prove identity or overwrite the master phone.
Test compatibility after version change
Import a small sample of a new schema and compare names, types and states. Do not merge old analysis directly across versions.
The Libya acceptance sentence
Correct fields, states, reconnection and purpose define completeness; column count has no quality meaning.
