## Report Properties

### Summary/General Information

The following is a summary of general information about the report.
Report general information:

Report file name | https://cleanscore.xbrlcloud.com/user/share/me.com/Essentials/component2/instance.xml
Report identifier (target namespace) | http://www.xbrlsite.com/proof
Prefix | proof

Taxonomy version:

Taxonomy version | http://xbrlsite.azurewebsites.net/2016/conceptual-model/cm-roles

### Verification Summary

The goal is to create a verifiably correct true and fair representation of a reporting entity's financial information. The report should be complete, correct, consistent, accurate. The report should have fidelity and integrity.

|  |  | List | List | List | List | List | List
--- | --- | --- | --- | --- | --- | --- | --- | ---
All Components (Networks/Tables) | Status | Count of Relations | XBRL Technical Syntax Rules | Model Structure Rules | Business Rules (a) | Roll Up Rules (b) | Other Manual Review Tasks | Other Rules and Best Practice Tasks
Automated summary | Completed | 11 | OK | OK | OK | OK | Not Specified (c) | OK
Automated rules defined |  |  | 205 | 7 | 3 | 1 | 0 | 0
Automated rules executed which PASSED |  |  | 205 | 7 | 3 | 1 | 0 | 0
Automated rules executed which FAILED |  |  | 0 | 0 | 0 | 0 | 0 | 0
Manual summary | Completed | 11 | OK | OK | OK | OK | Not Specified (c) | OK
Manual rules defined |  |  | 0 | 0 | 1 | 1 | 0 | 31
Manual rules executed which PASSED |  |  | 0 | 0 | 0 | 0 | 0 | 31
Manual rules executed which FAILED |  |  | 0 | 0 | 0 | 0 | 0 | 0

(a) Some anomalies, such as those associated with Roll Forward and Member Aggregations, are automatically generated by XBRL Cloud. More often than not, there is a problem in the XBRL such as an inverted label role, an inverted number, a missing calculation, a translation (from HTML to XBRL) error, or some other problem. In a small number of cases, the choice of modelling, or the lack of inverted label is intentional.
(b) Roll ups are expressed using the XBRL calculations technical syntax. Roll ups which pass are listed in automated testing results as "OK". Roll ups which fail are listed in the manual verification rules as requiring manual verification. This is because XBRL calculations verification can properly detect roll ups which pass, but due to a known limitation of XBRL calculation validation, such validation cannot be certain that a roll up which is not deemed to work correctly is a failure. As such, to avoid false interpretation of non-passing XBRL calculation results as failures; they are deemed to be "inconsistencies" by the XBRL specification. Therefore, calculation inconsistencies must be manually examined to verify whether a non-passing calculation is a true error or a validation test which is not applicable to facts within a particular network.
(c) "Not Specified" indicates that there are no rules for this business rule set. This section must be evaluated manually as the Evidence Package is not providing any guidance in this area.

### Report Objects Summary

The report objects of an SEC XBRL financial report can be grouped into categories. The different report objects have different properties. Categorizing these report objects and using those groupings can help in the verification process. Relations between report objects can be better understood when leveraging these categories.

Components | 1
Networks | 1
Tables | 1
Axes | 2
Members | 0
Line Items | 1
Abstracts | 2
Concepts | 5
Facts | 6
Parenthetical explanations | 1
Structural relations | 11
Business rules | 4

### Component Summary

A component is a combination of a network and a table. All facts exist within one or more networks. All facts also exist within one or more tables, be that table an explicitly defined [Table] or an implied table.

# | Title | URI | Table (Explicit or Implied)
--- | --- | --- | ---
1 | 06-Cash Flow | http://www.xbrlsite.com/proof/role/CashFlow | Cash Flow [Hypercube]