epic: Program Component

[zmalatrax]

In order to prove that the Instruction table is effectively a sublist (ordered subset) of the program (ProgramMemory) that was run by the brainfuck_vm, we actually need a component representing the program itself (to use the LogUp protocol).

No need to add local constraints to the Program component, simply on the logUp column shared with the Instruction component.
As there is no local constraints, no need to flatten two consecutives rows (i.e. entries) into a single row as in the Instruction component.

Note: Should we enforce a sorting on ip, and add constraints that ip increases by one, starting at 0? Adding a constraint that ip must always be increased by one allows for the uniqueness of ip (unless it's a dummy row)

Trace

ip	ci	ni	d

Trace

Preview Give feedback

1. feat: add a ProgramTable struct #151
   +0
   
2. feat: implement From<&Vec<Registers>> for ProgramTable #152
   +0
   
3. feat: implement the trace evaluation for ProgramTable #153
   +0
   
4. feat: add Program trace to the prove_brainfuck entrypoint #154
   +0
   

Interaction Trace

Preview Give feedback

1. feat: construct the required lookup elements for the Program interaction trace #155
   +0
   
2. feat: generate Program interaction trace #156
   +0
   
3. feat: add Program interaction trace to prove_brainfuck entrypoint #157
   +0
   

Component

Preview Give feedback

1. feat: scaffold Program component #158
   +0
   
2. feat: add constraints to Program component #159
   +0
   
3. feat: add Program component to prove_brainfuck entrypoint #160
   +0