Jitto Build
Raw files in.
Report tables out.
Jitto Build turns your raw data into tested warehouse tables. It checks each table against its source before the next step starts, so a report never sits on numbers nobody checked.
Bring a set of exports. We will build from them with you.
Report tables
6Equal to the report
6Not equal
0| Report chart | Rows | Result |
|---|---|---|
| Net flows by fund | 4 | Equal |
| Market value by fund | 4 | Equal |
| Profit and loss by month | 3 | Equal |
| Traded value by month | 3 | Equal |
| Commission rate by broker | 4 | Equal |
| Settlement fails by week | 14 | Equal |
How a build runs
Eight steps.
Each one waits for the last.
Look
List every table, and name the mess: backup copies, text columns that hide structured data, and logs of events.
Measure
Count the rows. Suggest a key only when the count shows that it has no blanks and no repeats.
Plan
Write down which tables to stage, which events to keep, and how often each one should refresh.
Load
Copy each table into the warehouse with the same number of rows as the source.
Model
Write the models as code and run them, with a test on every model.
Check
Compare each table with its source, by row count and by key. Both sides are only read, never changed.
Serve
Publish each table as metrics, and test that every definition runs.
Watch
Compare each table's age with how often it should refresh, and say what is due next.
What a person decides
Build does the work.
You keep the say.
A record for every step
Each step writes what it read, what it made and whether it passed. The next step does not start until it passed.
Your reports as the target
You describe each chart once: its source, its grouping and its measure. Build makes a table that gives the same numbers.
Questions only you can answer
Build will draft a description of each report table: its columns, their types and its key. The owner, the purpose and who uses it stay blank for a person. This part is still in review.
A terminal anyone can take over
Build works in a real terminal. Anyone on your team can take over the session and carry on.
The check fails first
The check fails before the change and passes after. The record shows both.
A person reviews and merges
Changes wait for a person's review. Approval is refused while a check is red, and nothing merges until a person says yes.
Questions
Before you build.
What does Build need to start?
Your data. In the sample above, that was a folder of exported files: trades, positions, prices, profit and loss, and fund flows.
How do I know a table is right?
Each table is compared with its source before the next step runs. For a report, the table must give the same numbers as the report.
Will Build guess what a table is for?
No. It writes down what it can measure. What only a person knows stays blank and is asked as a question.
Is the sample real data?
No. Every fund, trade and broker in it is invented.