You are an expert Verilog hardware designer working on a complete FPGA or ASIC project. You are given the full source code of a Verilog project. One of the modules in the project is incomplete — its implementation is missing and marked with:

// >>> Module Implementation Begin

// <<< Module Implementation End

Your task is to complete the missing implementation so that the entire project functions correctly. You must infer what the missing module or logic is supposed to do by analyzing the rest of the codebase: module names, signal connections, instantiations, comments, and usage patterns.

Follow these rules:

1. Only generate Verilog code to go between the `// >>> Module Implementation Begin` and `// <<< Module Implementation End` comments.
2. Use Verilog-2001 syntax. Ensure the code is synthesizable.
3. Assume the goal is a working, integrated hardware design — your code must make the whole system function as intended.
4. Analyze the naming, I/O ports, and how the module is instantiated or used in other parts of the project.
5. Implement correct behavior based on design context. Do not guess randomly — reason it out.
6. Avoid vendor-specific features unless explicitly required.
7. Do not output comments, explanation, or anything outside the required code region unless explicitly asked.

Your output should contain **only the Verilog code** that fits inside the marked region.

/*
 * Claudio Talarico
 * 4-bit up/down binary counter with enable
 */

`default_nettype none

module tt_um_claudiotalarico_counter (
    input  wire [7:0] ui_in,    // Dedicated inputs
    output wire [7:0] uo_out,   // Dedicated outputs
    input  wire [7:0] uio_in,   // IOs: Input path
    output wire [7:0] uio_out,  // IOs: Output path
    output wire [7:0] uio_oe,   // IOs: Enable path (active high: 0=input, 1=output)
    input  wire       ena,      // always 1 when the design is powered, so you can ignore it
    input  wire       clk,      // clock
    input  wire       rst_n     // reset_n - low to reset
);
    
 // instantiate top level 
    tiny u1(.clk(clk),
            .rst_n(rst_n),
            .test(ui_in[0]),
            .ud(ui_in[1]),
            .en(ui_in[2]),
            .cnt(uo_out[3:0])
 );  
  
 // All output pins must be assigned. If not used, assign to 0.
 assign uo_out[7:4]  = 0; 
 assign uio_out = 0;
 assign uio_oe  = 0;

 // List all unused inputs to prevent warnings
    wire _unused = &{ena , uio_in , ui_in[3], ui_in[4], ui_in[5], ui_in[6], ui_in[7], 1'b0};

endmodule


// tiny.v
// top level

module tiny(rst_n, clk, ud, en, test, cnt);
  parameter n = 4;
  input rst_n, clk, ud, en, test;
  output [n-1:0] cnt;

  wire sclk;

  //instantiate clkdiv
  clkdiv u1(.clk(clk),.rst_n(rst_n),.test(test),.sclk(sclk));

  //instantiate counter
  counter u2(.sclk(sclk),.rst_n(rst_n),.en(en),.ud(ud),.cnt(cnt));

endmodule


// file: clkdiv.v
// clock divider 
// test mode: sclk is only 8 times slower than clk

module clkdiv(clk, rst_n, test, sclk);
  parameter n = 26;
  input clk, rst_n, test;
  output sclk;

  reg [n-1:0] count; 
  wire sclk;

  always @(posedge clk, negedge rst_n)
  begin	  
    if (~rst_n)
      count <= 0;
    else
      count <= count + 1;
  end

  assign sclk = test == 0 ? count[n-1] : count[2];

endmodule


// file: counter.v
// 4-bit binary up/down counter with enable 

module counter(sclk, rst_n, en, ud, cnt);
// >>> Module Implementation Begin

// <<< Module Implementation End
endmodule




Reference solution:
rtl/generated.v:   parameter n = 4;
  input sclk, rst_n, en, ud;
  output reg [n-1:0] cnt;

  always @(posedge sclk, negedge rst_n)
  begin
    if(~rst_n)
      cnt <= 0;
    else if (en)
      if (ud)
        cnt <= cnt + 1;
      else
        cnt <= cnt - 1;
  end